Model-View-Presenter
For the past year or so, Martin Fowler has included the pattern Model-View-Presenter, or MVP, in his upcoming addendum to Patterns of Enterprise Application Development. Due to apparent confusions between MVC and MVP, Fowler has now split this pattern into what he's calling “Passive View” (http://martinfowler.com/ea... and “Supervising Controller/Presenter” (http://martinfowler.com/ea... (Now what am I to do! ;) Passive View...
I've been working on an article for the past few weeks concerning the usage of the Model-View-Presenter pattern with ASP.NET. The article has been completed and uploaded to http://www.codeproject.com/... I hope you find this article useful. Please feel free to raise your questions and/or concerns. Billy...
On a previous post, I mentioned my introduction to Model-View-Presenter (MVP). I've now gotten a chance to try it out on a new project and have been very pleased with the results thus far. MVP provides an approach for clean separation of concerns within the ASP.NET presentation layer without dismissing the page event model. MVP sees the code-behind, along with the ASPX page, as strictly part of the view and provides a patter to treat it accordingly. Although the pattern itself is easy to understand...
Arguments abound for whether or not ASP.NET provides adequate MVC. On the other hand, many feel Page Controller and Front Controller are the way to go. Others feel the entire page model should be abandoned in the favor of something more attuned to Ruby on Rails such as Castle MonoRail. For me, I've always liked the page event model and feel user and server controls are wonderful, but have struggled with making the code behind strictly part of the view. I believe Model-View-Presenter is the answer....