90 likes | 215 Vues
This article explores the differences between ASP.NET MVC and MVP (Model-View-Presenter) architectural patterns, focusing on their approaches to separation of concerns, responsibilities, and testability. It discusses how both patterns manage views, models, and controllers/presenters, emphasizing the impact on application design and maintainability. This comparison helps developers choose the most suitable pattern for their projects based on specific requirements. Learn more about the benefits of using architectural patterns for better software architecture and design.
E N D
A Comparison of ASP.NET MVC and MVP
Separation of Concerns Responsibilities Testability Why use an architectural pattern?
View • Display Information • Controller/Presenter • Get data from the Model • Send it to View for display • Model • Everything else Model – View – *
Model – View – Controller View Controller Model
Model – View – Presenter View Presenter Model
Model-View-Presenter http://msdn.microsoft.com/en-us/magazine/cc188690.aspx http://www.pnpguidance.net/Post/UnityIoCDependencyInjectionASPNETModelViewPresenter.aspx Model-View-Controller http://haacked.com/ http://jeffreypalermo.com/ Resources
Twitter: @leebrandt Email: leebrandt@gmail.com Blog: www.codebucket.org Thank You