Chapter 1. ASP.NET MVC controllers
They always say time changes things, but you actually have to change them yourself.
I think ASP.NET Web Forms started getting old the day that Ajax conquered the masses. As some have said, Ajax has been the poisonous arrow shot in the heel of ASP.NET—another Achilles. Ajax made getting more and more control over HTML and client-side code a true necessity. Over time, this led to different architectures and made ASP.NET Web Forms a little less up to the task with each passing day.
Applied to the existing ASP.NET runtime, the MVC pattern produced a new framework—ASP.NET MVC—that aligns web development to the needs of developers today.
In ASP.NET MVC, each request results in the execution of an action—ultimately, ...