Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • I asked a similar question a while back: Where to put User Interface/Domain Model manipulation logic (transferring data from the view to Domain Model). I don't think it answers you question, but this exposes the biggest problem with examples of MVC. They focus on the mechanical way to get things working, and not where this UI design pattern fits into the overall architecture of an application. MVC is but one piece of the architecture. Commented Nov 19, 2021 at 18:23
  • Thanks @GregBurghardt. It at least give me an understanding of the problem of MVC in an stateless interface. Commented Nov 19, 2021 at 18:33
  • Another question (that I answered, actually): Why do backend web frameworks use "MVC" when they have no persistent UI to update?. Commented Nov 19, 2021 at 19:01
  • While this sample is unfortunately built around ASP.NET Core 2.1, it demonstrates a greatly improved project structure for Microsoft's "Contoso University" than the original (dividing the app into "Features", splitting logic away from Controllers). The author is also responsible for MediatR, FluentValidator and AutoMapper (which are all great libraries to use with ASP.NET Core + EF Core) so the sample includes the benefits of those too: github.com/jbogard/ContosoUniversityDotNetCore Commented Nov 20, 2021 at 11:06