Chapter 1 ASP.NET MVC controllers
Chapter 2 ASP.NET MVC views
Chapter 3 The model-binding architecture
Chapter 4 Input forms
Chapter 5 Aspects of ASP.NET MVC applications
Chapter 6 Securing your application
Chapter 7 Design considerations for ASP.NET MVC controllers
Chapter 8 Customizing ASP.NET MVC controllers
Chapter 9 Testing and testability in ASP.NET MVC
Chapter 10 An executive guide to Web API
Chapter 12 Making websites mobile-friendly
Chapter 13 Building sites for multiple devices
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, a method on a specific class. The results of executing the action are passed down to the view subsystem along with a view template. The results and template are then used to build the final response for the browser. Users don’t point the browser to a page, they just place a request. Doesn’t that sound like a big change?