Webforms vs MVC

Webforms vs MVC

We will learn...

• WebForms Architecture, Life Cycle & Advantages
• MVC Architecture, Life Cycle & Advantages
• Common in WebForms and MVC
• WebForms vs MVC

Recommended Videos:

• ASP.NET Framework vs ASP.NET Core
• What is ASP.NET Blazor

Advantages of Webforms

• It provides Easy & RAD model for developers, coming from WinForm development.
• Development supports state - Gives the illusion that a web application is aware of what the user has been doing, similar to Windows applications. I.e. Makes 'wizard‘ . Web forms does a great job at hiding a lot of that complexity from the developer.
• Rapid Application Development (RAD) - The ability to just 'jump in' and start delivering web forms. The web forms model probably has less of a learning curve to less experienced developers. In the end, it comes down to the level of expertise of the developer and what they are comfortable with and Learn as you go.
• Larger control toolbox - ASP.NET Web Forms offers a much greater and more robust toolbox (web controls) with solid data binding whereas MVC offers a more primitive control set relying more on rich client-side controls via jQuery (Javascript).
• Master Pages, ASP.NET Identity, State Management, Security, Event driven,
• Separate UI, Drag and Drop Interface and Mature.

Advantages of MVC

• Enables the full control over the rendered HTML.
• Provides clean separation of concerns (SoC).
• Enables Test Driven Development (TDD).
• Easy integration with JavaScript frameworks.
• Following the design of stateless nature of the web.
• RESTful urls that enables SEO.
• No ViewState and PostBack events
• Proper AJAX, e.g. JSONResults no partial page postback.
• No renaming of the HTML IDs.
• Clean HTML = no bloat and having a decent shot at rendering XHTML or standards compliant pages.
• It works well for Web applications that are supported by large teams of developers and Web designers

Common in WebForm and MVC

• ASP.NET Web Forms and MVC are two web frameworks developed by Microsoft - they are both good choices.
• Each of these web frameworks offers advantages/disadvantages - some of which need to be considered when developing a web application.
• Authentication, authorization, configuration, compilation and deployment are all features that are shared between the two web frameworks.

MVC vs WebForms

• Separation of concerns (SoC) - From a technical standpoint, the organization of code within MVC is very clean, organized and granular, making it easier for a web application to scale in terms of functionality.
• Integration with client side tools - More than ever, web applications are increasingly becoming as rich. MVC integrate with such toolkits (such as jQuery) with greater ease and more seamless than in Web Forms, MVC not very easy to learn.
• Search Engine Optimization (SEO) Friendly/Stateless URL's are more friendly to search engines (i.e. mywebapplication.com/users/ 1 - retrieve user with an ID of 1 vs mywebapplication/users/getuser.aspx (id passed in session)).
• MVC is stateless - this removes the headache of users who open multiple web browsers from the same window (session collisions). MVC adheres to the stateless web protocol rather than 'battling' against it.
• Works well with developers who need high degree of control  - Many controls in ASP.NET web forms automatically generate much of the raw HTML you see when an page is rendered. With MVC, it lends itself better towards having complete control with what is rendered and there are no surprises.
• MVC generated HTML forms typically are much smaller than the Web forms which can equate to a performance boost - something to seriously consider.
• Test Driven Development (TDD) - You can more easily create tests for the web side of things. An additional layer of testing will provide yet another layer of defense against unexpected behavior.

Next : Comparison MVC & MVP