- Web Forms is hard to test as compared to ASP.NET MVC application
- ASP.NET MVC requires you to specify every little bit of HTML as comared to web forms.
- The Separation of Concerns (SoC) is not proper in Web Forms Development. In MVC there is a clear separation between your UI and code.
- Web Forms was designed to abstract the Web machinery whereas ASP.NET MVC was designed with testability and DI in mind
- ASP.NET MVC takes you towards a better design of the code
- ASP.NET MVC is not EventDriven where asp.net web forms use events.
- ASP.NET MVC does not have third party control support.Web forms provide rich support for third party controls.
- In Web Forms to achieve statefulness, state of every page stored in viewstate which often rendered on client page as a hidden field.
- In ASP.NET MVC no viewstate is ever required to persist the state of the page.
- In Web Forms the post back model of ASP.NET page makes it harder for search engines to rank the page. No posback is needed in ASP.NET MVC.
Friday, September 9, 2011
Explain how the ASP.NET MVC framework differs from the current ASP.NET Web Forms
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment