It is really a big question whether to use MVC framework or to use classic asp.net. But few point to remember:
The MVC Framework doesn’t support classic postback and viewstate and doesn’t consider any URL as the endpoint to a physical server file to parse and compile to a class. In ASP.NET, you have a 1:1 correspondence between a URL and a resource.
In the MVC Framework, a URL is seen as the mean to address a logical server resource, but not necessarily an ASPX file to parse.
Representational State Transfer, or REST:
REST is an architectural pattern that defines how network resources should be defined and addressed in order to gain shorter response times, clear separation of concerns between the front-end and back-end of a networked system. REST is based on three following principles:
– An application expresses its state and implements its functionality by acting on logical resources
– Each resource is addressed using a specific URL syntax
– All addressable resources feature a contracted set of operations
The MVC Framework fulfills it entirely. But classic asp.net supports PostBack data model.
Web applications developed with ASP.NET MVC are even more SEO (Search Engine) friendly.
In case of MVC developer has to do more coding.
if you want know about Asp.Net MVC life cycle Asp.Net MVC Life Cycle and Various State Management Techniques in Asp.Net MVC
SharePoint Online FREE Training
JOIN a FREE SharePoint Video Course (3 Part Video Series)