Model View Controller in asp.net

1) http://www.asp.net/mvc/videos/aspnet-mvc-controller-overview
2) http://www.beansoftware.com/ASP.NET-Tutorials/MVC-Architecture-Model.aspx
3) http://www.dotnetuncle.com/wiki/ASPNET-MVC-Framework.aspx
4) http://www.slideshare.net/maartenba/msdn-aspnet-mvc
5) http://msdn.microsoft.com/en-us/library/dd394709.aspx
6) http://www.slideshare.net/jesschadwick/introduction-to-aspnet-mvc-3353914 

7) What is the difference between 3-tire architecture and MVC Architecture/Model? 

Ans: A fundamental rule in three-tier architecture is the client tier never communicates directly with the data tier; in a three-tier model all communication must pass through the middleware tier.

It’s liner architecture. This addresses the question of how to pass information between a user and a database. Where as MVC is a triangular architecture: the View sends updates to the Controller, the Controller updates the Model, and the View gets updated directly from the Model. This addresses questions of how a user interface manages the components on the screen.

Presentation layer(aspx, aspx.cs) = view and controller MVC (aspx, aspx.cs)
Application Layer = Model of MVC
Database layer = DB layer of MVC

Advantages of using MVC in ASP.NET

• There's no duplicated code.
• The business logic is encapsulated; hence the controller code is transparent and safer.
• The business logic can be used in several front ends like Web pages, Web services, Windows applications, services, etc.
• Exception handling is well managed showing the user only digested error messages.
• Testing every part of an application is easier as it can be done separately using automated methods.
• Application changes are easier to apply as they are focused in one part of the architecture only.