Saturday, August 22, 2009

MVC Framework

Model-View-Controller (MVC) is a classic design pattern often used by applications that need the ability to maintain multiple views of the same data. The MVC pattern hinges on a clean separation of objects into one of three categories — models for maintaining data, views for displaying all or a portion of the data, and controllers for handling events that affect the model or view(s).
Because of this separation, multiple views and controllers can interface with the same model. Even new types of views and controllers that never existed before can interface with a model without forcing a change in the model design.
How It Works
The MVC abstraction can be graphically represented as follows.
Events typically cause a controller to change a model, or view, or both. Whenever a controller changes a model’s data or properties, all dependent views are automatically updated. Similarly, whenever a controller changes a view, for example, by revealing areas that were previously hidden, the view gets data from the underlying model to refresh itself.

ASP.NET MVC Framework tutorial links
 1. http://weblogs.asp.net/scottgu/archive/2007/10/14/asp-net-mvc-framework.aspx

 2. http://weblogs.asp.net/scottgu/archive/2007/11/13/asp-net-mvc-framework-part-1.aspx

3. http://www.asp.net/Learn/mvc/tutorial-21-cs.aspx

4. http://msdn.microsoft.com/en-us/magazine/cc337884.aspx

5. http://stephenwalther.com/blog/category/4.aspx?Show=All