by Giselle N
The article I read this week was about which ASP.NET option is the best for web developers: the older ASP.NET Web Forms, or the newer ASP.NET MVC. Although ASP.NET MVC might seem like the obvious choice because it has a lot of new improvements, the author goes onto to say that ASP.NET MVC has greater startup costs and some applications in MVC are a huge change from Web Forms. The main purpose of developing ASP.NET MVC was to help separate data, business logic, and presentation to the user, which has shown good results. However, just because MVC applies patterns to reduce overlapping (mainly business logic and presentation), it is no reason as to why people should spend more money on it, the author says. Still, MVC not only applies these patterns, its has other advantages opposed to Web Forms including: greater testability, separation of concern, ease of modification, and to sum up; it is just technically more advanced since it was released 5 years after Web Forms. However, the author says, when it comes to the main functions, there is really no difference between the two. Yet, people are still choosing ASP.NET MVC because they were just not happy with ASP.NET Web Forms. To others, it’s not just because they are unhappy with Web Forms, it’s that MVC “overcomes one of the best selling points of ASP. NET Web Forms when it was introduced a decade ago: Web Forms shielded developers from the nitty-gritty details of HTML. In contrast, ASRNET MVC stays closer to the metal of HTML and HTTP, and it gets rid of the thick abstraction layer built on top of Web Forms (viewstate, server controls, page controllers, eventbased page life cycle).” Further, it offers…”control over HTML and interaction with inline JavaScript…” Because of this, MVC also lets developers create AJAX applications easier and produces cleaner and more testable code.


I thought this article was interesting. I thought it was obvious as to why ASP.NET MVC was the better choice just because ASP.NET Web Forms was released about oh, a decade ago in 2002. However, it’s been a while since ASP.NET MVC has been released in 2007-2008 as well. Still, if developers are content with using Web Forms, there is no real reason to switch, as it will save them money, which is ASP.NET MVC’s biggest disadvantage, as the author suggests. Though, I don’t really see it as a disadvantage if you are getting your money’s worth, with all the improvements and advantages MVC has. It really just depends on the developer. Like the saying, “if it ain’t broke, don’t fix it.” People had switched to MVC because they were unhappy with Web Forms, but if some are fine with it, then they should keep using it.


Esposito, D. (2011). Which ASP.NET is better? InformationWeek, (1307), 50-50,52. Retrieved from on June 3, 2012.

2 thoughts on “ASP.NET MVC vs. ASP.NET Web Forms

  • June 3, 2012 at 6:48 pm

    Great article! In the end, it’s always going to be up to the developer what they want to use. I personally would go with ASP.NET MVC because it’s cooler 😛 Thanks for posting!

  • June 3, 2012 at 7:00 pm

    Great article!! I also wrote about ASP.NET VS PHP but I believe it mostly come down to preference and which one you are comfortable with.

Comments are closed.