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 like having control over exactly what’s going on under the hood (the MVC way), but I’m also lazy, and don’t like writing tons of javascript GUI things.
Should I or should I not switch to MVC?
Thanks,
Nestor
It depends. If you are good at writing Webforms applications, you have lots of ASP.NET server controls already at your disposal, and you don’t need a lot of finesse (read: code behind) in your application, then Webforms is probably a better choice.
On the other hand, if you like applications that are highly performant and cleanly architected, need precise control over your markup, and would like your application to be testable, then ASP.NET MVC is a better choice.
There are lots of easy to use JQuery widgets available for ASP.NET MVC, so your dislike of Javascript shouldn’t hold you back. But there is a learning curve to MVC, so if you are averse to learning new things, I would stick with Webforms.