Why Asp.Net MVC instead of Asp.Net?

Traditional Asp.Net is good idea, but there are some issues in practical.

The actual problems in Traditional Asp.Net mentioned below.

 

  • To maintain state between we are using ViewState in Traditional Asp.Net. That results giant blocks of data transferred between client and server. This data is hundred kilo bytes in size in real world applications and it goes back and forth between requests, frustrating the users and requires heavy bandwidth.
  • In Asp.Net Server controls renders themselves as HTML controls on browser, but not necessarily the HTML you want.  It may differ in ID’s of the controls or CSS styles.
  • In Traditional Asp.Net, there is no automated testing facility for Applications.

 

The above problems are solved by Asp.Net MVC.


I will explain how Asp.Net MVC solves the problems with Traditional Asp.Net in my later posts with examples.