When it comes to choosing which framework to work with, you need to think about several key points that differentiate conceptually MVC and WebForms models.
Following is a comparison between the two frameworks that can help you when choosing one or the other when deciding which model suits your web application requirements
MVC fully embraces HTTP.
Controllers in MVC are decoupled from any state and can be easily tested and mocked. Thus, automatic unit testing is easily supported.
Rich routing capabilities.
MVC supports a number of view engines, such as Razor. In addition, you can implement your own view engine.
You can also use container models, such as Dependency Injection and Inversion of Control.
You can extend the routes, controllers, filters, and actions in MVC and also to define your own HTML Helpers.
The important point to note is that one framework does not replace the other, but they serve different purposes and requirements. For example, an advantage of ASP.NET WebForms is the vast infrastructure and ecosystem built around it. On the other hand, working with ASP.NET MVC makes a lot of sense for web pages.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
For developers: Develop with Sitefinity and ASP.NET MVC
Copyright © 2022 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity