Coding to MVP but I need more
I have spent all day today coding a asp.net app to the MVP pattern and it's been an interesting exercise. It's a different way of thinking when developing in contract terms and can feel a little longer winded than normal, the ability to abstract the view and test the presenter makes it all the worth the while. What strikes me is that webforms is not a great for patterns and I hope it gets better at it both for MVP and MVC. In an ideal world it would be great to see
clean abstraction between my view and the presenter/controller.
the presenter or controller to be created as a normal class and unit testable like any other class
for the asp.net controls to use more lower level controls at their base, I don't need to create a IContext because the HttpContext inherits from a Context object that I can expose to my tests.
The event rigs to be built into the framework, currently you have to expose event handlers and re-raise the events for each control event. This boils down to the view being a pure view and the code behind a pure controller or presenter.