"ASP.NET Webforms MVP" as an alternative to "ASP.NET MVC" [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 12 years ago.

Some days ago I discovered a "thing" which is called the ASP.NET MVP framework ( http://webformsmvp.com/ )

What do you think of that ? Is it worth to take a look on it ? Has anybody already experiences with that ? I come from the "webform side" (and also from the开发者_如何转开发 desktop development) and really don't want to move to ASP.NET MVC for the next time. Would the MVP pattern a good alternative, especially for "webform fans"?

At my projects RAD capabilities are very important. My clients often want to see very soon a visual prototype. So for me classic ASP.NET webforms is the better choice.

Or should (I) we accept, that webforms will have no future ? What are the plans of Microsoft?

---

This is interesting, to find a balance may be important. To many companies I've worked with, the faster the better and quality is not very important. For others, total control is necessary and MVC is a great answer.

I've been working with MVC since version 1 beta and with WebForms since .net 1.0. I must honestly say that MVC has made my life simpler when it comes to code reuse, Iterative development and flexibility. It allows me to have a faster response time, when they make last minute changes.

Having built my self a foundation (Which I also have for ASP.Net) I was able to reduce the amount of setup time for a project to almost nothing. This also gives me a good head start.

Both frameworks have their advantages and I would be curious to see what come out of MVP.

I'd like to hear from people who have gone to production with MVP.