As Robert suggested, if you want to gain all the benefits from building fully testable modules today, then the new MVP Framework that is included in DNN 5.3 is the right way to go. This is a full featured implementation based on the WebFormsMvp codeplex project.
In addition over time, both the underlying WebFormsMvp project and our own implementation will likely evolve to provide mor features.
For example, in the next feature release we will be adding some extra helper methods that can be used in the presenter class:
- LocalizeString - the LocalResourceFile is automatically "wired" up in the base classes and all you need to do is call LocalizeString(key) to get localized strings in your presenter
- ShowMessage - there a couple of overloads which allow developers to add skin messages - again this is wired up in the base classes so all developers have to do in the presenter is call this method
- ProcessModuleLoadException - this method provides the behaviour that can today be used in PortalModuleBase in the Presenter class.
In addition, Tatham and Damian the creators of the WebFormsMvp project are planning to add convention based presnter binding so you no longer will have to add an attribute to the View to indicate which presenter to use, much the same way the MVC uses conventions for Controller and Actions.
With regard to MVC, currenttly the code in the dnnlabs codeplex project, supports the default controller (HomeController) and action (Index), so as long as thats all you need it works today. However the indtention is to to be able to support full routing and use of the Helpers to build robust MVC style modules.