Using C# Interfaces as View Models With ASP.NET Core 3.1 Razor Pages in MVVM Design

The post discusses using C# interfaces as view models with ASP.NET Core 3.1 Razor Pages in an MVVM design pattern, exploring limitations and potential alternatives for this approach. The author provides a case study application to demonstrate the use of interfaces for view models and tests their limits by attempting to bind them to the page model. The post concludes that while using interfaces as view models can add flexibility, it may not be practical in all cases due to constraints on binding and abstraction. It suggests considering additional design patterns, such as inversion of control containers and dependency injection, to achieve further abstraction and decoupling.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.