Timeline for In an MVC Application, What Goes Where?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 20, 2021 at 11:06 | comment | added | Ben Cottrell | 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 | |
| Nov 20, 2021 at 5:00 | vote | accept | careLess | ||
| Nov 19, 2021 at 22:45 | answer | added | Christophe | timeline score: 5 | |
| Nov 19, 2021 at 20:01 | review | Close votes | |||
| Nov 27, 2021 at 3:06 | |||||
| Nov 19, 2021 at 19:01 | comment | added | Greg Burghardt | Another question (that I answered, actually): Why do backend web frameworks use "MVC" when they have no persistent UI to update?. | |
| Nov 19, 2021 at 18:33 | comment | added | careLess | Thanks @GregBurghardt. It at least give me an understanding of the problem of MVC in an stateless interface. | |
| Nov 19, 2021 at 18:23 | comment | added | Greg Burghardt | 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. | |
| Nov 19, 2021 at 18:22 | history | edited | careLess |
edited tags
|
|
| S Nov 19, 2021 at 18:10 | review | First questions | |||
| Nov 19, 2021 at 20:40 | |||||
| S Nov 19, 2021 at 18:10 | history | asked | careLess | CC BY-SA 4.0 |