I\'m reading about ASP.net MVP pattern over this weekend and it seem like even the most simple task take too much effort if do it in MVP pattern the pay off seem to be at larger
I would recommend reading the following two links to get you up to speed on MVP and MVC :
Should you switch over?
Based on what you've told me I would recommend that you use the Passive MVP model mentioned in the article above.
My main assumptions are:
Your View (codebehind + aspx) essentially become dumb and just perform simple tasks:
I've used this model extensively for Web Forms development and I couldn't imagine not being able to Unit Test my Model and Presenter code. Once you establish your base model which doesn't take very long and seen the power of Unit Testing, working with Web Forms becomes enjoyable.
Some links to MVP stuff that the model I've used is based on:
I would also recommend that you learn MVC to.
When time permits, take an existing App and port it to MVC. This way your sole focus is getting to know MVC and when you move logic into the MVC pattern, you'll discover things that you implemented in WebForms and never gave much thought to but now need to solved in another way. Great way to compare the patterns and see what works for you.
Hope this helps, feel free to ask any questions.