Timeline for Which pattern to use with a typical Web Form?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 17, 2020 at 17:45 | history | edited | Glorfindel | CC BY-SA 4.0 |
formatting
|
| Jul 19, 2012 at 5:32 | vote | accept | RPK | ||
| Jun 30, 2012 at 12:54 | comment | added | user53019 | The repository pattern is a little faster to implement and not as heavy as MVP / MVVM. The View is hitting the model directly instead of having an intermediary layer. Compared to MVP / MVVM it will be faster to implement with less code to write. OTOH, it will be more brittle because it is tightly coupled to the model / data access layer. Repository Pattern would possibly work for the circumstances you described, but if your project grows, you'll wish you had the intermediary Presenter / VM layer. | |
| Jun 30, 2012 at 12:07 | comment | added | RPK | Most of the applications I saw use Repository Pattern alone. What is reason? | |
| Jun 30, 2012 at 12:03 | comment | added | user53019 | MVP and MVVM are essentially the same. The Wikipedia article explains this too: MVP is the first derivative in this chain from MVC. Martin Fowler is credited with publishing the pattern and it deals with some of the challenges that a Controller can have in an event driven realm. MVVM was a refinement from there to take advantage of data binding between the view and view-model. | |
| Jun 30, 2012 at 11:54 | comment | added | RPK | I read about ASP.NET Model View Presenter framework at codeplex. Is MVVM available for Web Forms through any implementation? | |
| Jun 30, 2012 at 11:52 | history | answered | user53019 | CC BY-SA 3.0 |