Posted: September 26, 2012 in ASP.NET MVC3, ASP.NET MVCV 4
Tags: ,

Like i had anouced in my last post yesterday i had been the speaker in a session about Web and Cloud Development at the Launch event of Visual Studio 2012 in Portugal.

After my session some questions had arrived to my email. On off the most common questions was if ASP.NET MVC will kill ASP.NET WebForms. That was what made my write this post in the reality each technology has is one scope and is better at something i use them both depending on my goals.

Let’s take a look at the advantages of each one

Advantages of an MVC-Based Web Application

  • It makes it easier to manage complexity by dividing an application into the model, the view, and the controller.
  • It does not use view state or server-based forms. This makes the MVC framework ideal for developers who want full control over the behavior of an application.
  • It uses a Front Controller pattern this enables you to design an application that supports a rich routing infrastructure.
  • It provides better support for test-driven development (TDD).


Advantages of a Web Forms-Based Web Application

  • It supports an event model that preserves state over HTTP, which benefits line-of-business Web application development. The Web Forms-based application provides dozens of events that are supported in hundreds of server controls.
  • It uses a Page Controller pattern that adds functionality to individual pages.
  • It uses view state on server-based forms, which can make managing state information easier.
  • In general, it is less complex for application development, because the components (the Page class, controls, and so on) are tightly integrated and usually require less code than the MVC model.

For my point of view this is the most relevant points of each technology. Another point off choice can be the size of the development team envolved. If you have big and multidisciplinar teams MVC is better if you have produtivity issues and a very small team and you don t need to have full control of front end WebForms will be the winner.

I hope this post help you when you are looking for chose the right aim in the Microsoft Web development stack.

Any Question feel free to contact me.

  1. Nelson says:

    “if you have produtivity issues and a very small team and you don t need to have full control of front end WebForms will be the winner” hhhmmm MVC does provide a better back-end and better arquitecture to optimize and speed up development. So, with a good setup, in small teams MVC can be a better choice rather then WebForms.

    • amarreiros says:

      Yes i agree with you but if your time to market is short and you need a learning curve to go with ASP.NET MVC then WebForms are a better option. I am a great fan of MVC technologies but the true is that the event driven aproach is less complex then the MVC aproach and that’s a reason to make the choose in small teams wehere you have a very close opportunitty Window and a Team not familiar with MVC.
      If under contrary your team is already produtive and expert in MVC then MVC stills green no matter what, but we have always to remembre that from a developer prespective Event driven aproach makes tasks easy, especially for well trained .NET developers.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s