ASP.NET MVC vs. Web Forms

The July edition of MSDN mag has an interesting article by Dino Esposito that compares Web Forms And ASP.NET MVC. The author presents an excellent 100 feet view of ASP.NET MVC and I loved reading it. As I'm going to re-read it & recommend it to others, I've made a Reader's Digest version of it that squeezes the 3500+ worded article to about 500 words -

Benefits of ASP.NET Web Forms
  • ..stable and mature, supported by heaps of third party controls and tools.
  • To simulate stateful programming over the Web, ASP.NET Web Forms introduced features such as viewstate, postbacks, and an overall event-driven paradigm.
  • ..componentization of some ASP best practices
  • Productivity and rapid development of data-driven, line-of-business applications
Drawbacks of Web Forms
  • ..separation of concerns (SoC) has not been a natural fit with the Web Forms paradigm.
  • Automated testing of an ASP.NET Web Forms application is hard
  • ..postback model .. makes it harder for search engines to rank ASP.NET pages high.
  • ..excessively large viewstate is problematic

Benefits of ASP.NET MVC
  • ASP.NET MVC is a completely new framework for building ASP.NET applications, designed from the ground up with SoC and testability in mind....a working environment that enables, not penalizes, test-driven development (TDD)
  • No postbacks
  • No viewstate
  • ..stateless behavior, full control over every single bit of HTML, total script and CSS freedom.
  • ..leaner run-time stack ... the run-time stack of ASP.NET MVC is simpler and the difference is due to the lack of a page lifecycle.
  • unparalleled level of extensibility
Drawbacks of ASP.NET MVC
  • ..full control over HTML, JavaScript, and CSS, ASP.NET MVC means that you enter the Web elements manually....a step backward in terms of usability and productivity.
  • ..not something you can easily learn by experimenting....this may be the source of decreased productivity for the average Web Forms developer.
Interesting facts
  • ..the size of the viewstate decreased significantly in the transition from ASP.NET 1.1 to ASP.NET 2.0 when Microsoft introduced a much more efficient serialization algorithm.
  • Ruby-on-Rails has proved that MVC can also be a successful pattern for Web applications; and ASP.NET MVC confirms this.
  • ASP.NET MVC today lacks some level of abstraction for creating standard pieces of HTML. HTML helpers are just an interesting attempt to speed up HTML creation
  • Web Forms embraces the RAD philosophy whereas ASP.NET MVC is TDD-oriented
  • Web Forms goes toward an abstraction of the Web that simulates a stateful environment, while ASP.NET MVC leverages the natural statelessness of the Web and guides you towards building applications that are loosely coupled and inherently testable, search-engine friendly, and with full control of HTML.
  • ASP.NET MVC is not the only way to get SoC in ASP.NET.
  • Web Forms was designed to abstract the Web machinery.
  • ASP.NET MVC exposes Web architecture.
  • ASP.NET MVC was designed with testability and Dependency Injection in mind.
  • ASP.NET MVC takes you towards a better design of the code.
  • ASP.NET MVC is young and lacks a component model.
  • ASP.NET MVC is not anti-Web Forms.
  • Web Forms is a model based on the "Page Controller" pattern.
  • ASP.NET Web Forms doesn't prevent unit testing, but it requires much discipline and repetitive boilerplate coding to do so.
  • ..in ASP.NET MVC intrinsic objects are mockable as they expose interface and base classes.
  • ..control over HTML and SEO-friendly URLs, both advantages of ASP.NET MVC, can be achieved to some extent in Web Forms. ASP.NET 3.5 SP1, in particular, includes the URL Routing and History API for SEO

Also see:
ASP.NET MVC: What is it and should I use it?
Biggest advantage to using ASP.Net MVC vs web forms

Comments

  1. Bartek3/05/2011 04:15:00 PM

    In my opinion, the question is becoming blurred with a lot of the cool features of MVC making their way into Webforms. ASP.NET 4.0 added URL Routing, reduced ViewState, and greater control of the HTML mark-up produced by many ASP.NET controls, now the next version of Webforms will incorporate many more MVC features into Webforms. http://bit.ly/dNhBd8

    ReplyDelete

Post a Comment

Popular posts from this blog

Datawrapper Makes Data Beautiful & Insightful

Datawrapper is an online data visualization tool available at datawrapper.de that lets you create charts, maps and tables. Here's the list of the different visualizations you can create - Bar Chart Stacked Bars Grouped Bars Split Bars Bullet Bars Column Chart Stacked Columns Grouped Columns Lines Multiple Lines Area Chart Scatter Plot Dot Plot Range Plot Arrow Plot Election Donut Pie Chart Multiple Pies Donut Chart Multiple Donuts Choropleth map Symbol map Locator map Table It is self-funded by its customers’ subscription revenue. It also provides a good Free Plan .  The Datawrapper “Created with Datawrapper” attribution appears at the bottom of the chart if you use the free plan. However, you retain full copyright to your charts, maps, and tables. To remove the attribution, you’ll need to update to Custom or Enterprise plan. The Datawrapper River is a place to exchange charts and maps with other Datawrapper users. After adding a chart to the River, anyone can use it and customiz...
Read more

Maven Crash Course - Learn Power Query, Power Pivot & DAX in 15 Minutes

Image
In the Maven Crash Course " Learn Power Query, Power Pivot & DAX in 15 Minutes ", Chris Dutton walks through a hypothetical business case while showcasing the power of modern Excel tools like Power Query, Power Pivot and DAX. Power Query is used to extract, transform, and load data from external sources like SQL databases, PDF and CSV files. A relational model is created to join the tables without writing a single formula. Exploratory analysis is done using Power Pivot and Data Analysis Expressions (DAX). Data Analysis Expressions is the language that we can use to define new calculated columns and measures to enhance our Data Model instead of the traditional cell formulas that we'd typically use if our data was stored in worksheets. Pivot Charts and slicers are used to design a simple interactive report that the sales managers can use to analyze revenue trends and product performance.
Read more

GitHub Copilot Q&A - 1

Image
Key takeaways from the talk in Q&A format - What is GitHub Copilot and how does it work? GitHub Copilot is a suite of tools designed for code completion. It works by analysing the code and comments you type in your IDE and sending that context to GitHub. Copilot then uses OpenAI's language model (in December 2024, it is GPT 4o by default and you can also choose the preview versions of o1-mini & o1-preview if you like) to understand your intent and generate suggestions for code completion. You can then accept, reject, or modify these suggestions. What context does GitHub Copilot consider when making suggestions? Copilot considers the entirety of the file you are currently working on, not just the code from your cursor position upwards. It also analyses the content of other open tabs in your IDE, starting with those closest to the current tab. This helps Copilot focus on the most relevant information. Is it necessary to meticulously manage open tabs for Copilot to work effect...
Read more