The MVC pattern was invented in the 70s as part of Smalltalk.MVC divides your UI into three distinct objects: the controller, which receives and handles input; the model, which contains your domain logic; and the view, which generates your output.
Provides: A "separation of concerns” Significant control over rendered HTML Supports Unit Testing, TDD and Agile methodologies Encourages the use of design patterns by convention Encourages more prescriptive applications Extremely flexible and extensible
“Many companies have a huge investment in WebForms technology that they just simply arent going tothrow out - training, third party controls, experienceand so on. ““Many companies dont buy into the whole Unit Testpitch behind MVC. Many companies simply dont testat all.” Quotes from Mike Brind http://mikesdotnetting.com/
Quotes from Scott Guthrie’s blog onAbout Technical Debates (and ASP.NETWeb Forms and ASP.NET MVC debates inparticular)
So back to the question…Is it really worth moving from ASP.NETWebForms to ASP.NET MVC?It depends
Comparison Sites: http://coderjournal.com/2008/12/introducing-aspnet-mvc-part-2-aspnet-mvc-vs-webforms/ http://blog.gadodia.net/choosing-between-webforms-and-mvc/ http://msdn.microsoft.com/en-us/magazine/dd942833.aspx http://www.asp.net/web-forms/videos/how-do-i/choosing-the-right-programming-modelConverting from Web Forms to MVC: http://codingatilivedigitally.wordpress.com/2012/07/10/9-steps-to-switch-from-asp-net-web-forms-to-mvc/ http://www.asp.net http://aspdotnetmvc.com/ ASP.NET MVC in Action (1-4) Programming Microsoft ASP.NET MVC Programming Microsoft ASP.NET 4