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’m working on an industrial project build with ASP.Net WebForms.
We seriously think about switching our application into an ASP.NET MVC.
It will take us some time, so do you think ASP.Net WebForms is a bad practice and the time spent on switching to MVC will be gain later?
WebForms, if coded with proper design patterns and practices, are perfectly fine. I would only invest in switching to MVC if one of the following is true:
The current performance is severely deficient. In this case, a re-write might be unavoidable, and switching to MVC (which may force a proper separation of concerns upon you) could be a good choice.
You are expecting to perform a major upgrade which will be impossible due to the current solution being in an unmaintainable state. In this case, switching is again a reasonable option.
In general, you can have well-written and poorly-written applications in both WebForms and MVC (though as I said MVC makes it slightly more difficult to write poor applications.) If you have an acceptably performing and maintainable WebForms application, don’t waste your dollars converting it.