Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am trying to figure out what to take into consideration before porting my whole application to MVC 3.
I heard it built better for the web.
I’d like to point out that my current website is based heavily on the Membership API, Roles etc.. Built-In with the .NET framework.
Will everything work?
ASP.NET MVC also uses ASP.NET pipelines – so most of HttpModule base stuff works with ASP.NET MVC.
However, actual handler works quite differently – ASP.NET Webforms uses Page and Control trees while ASP.NET MVC uses completely different approach – controller handling request and view used for html generation. There is certainly a learning curve involved for migrating to ASP.NET Webforms to ASP.NET MVC.
You should be asking yourself what exactly would you gain by migrating to ASP.NET MVC – for example, do you get a lot of enhancements and viable life span is more than 2-3 years. These might be the few reasons for considering migration.