The ASP.NET MVC Framework is a web application framework that implements the model-view-controller pattern. Based on ASP.NET, it allows software developers to build a Web application as a composition of three roles: Model, View and Controller. A model represents the state of a particular aspect of the application. Frequently, a model maps to a database table with the entries in the table representing the state of the application. A controller handles interactions and updates the model to reflect a change in state of the application, and then passes information to the view. A view accepts necessary information from the controller and renders a user interface to display that.[1]
In April 2009, the ASP.NET MVC source code was released under the Microsoft Public License (MS-PL).[2]
The ASP.NET MVC Framework couples the models, views, and controllers using interface-based contracts, thereby allowing each component to be easily tested independently.
Release history
Release History
| Date |
Version |
Notes |
| 2007-12-10 |
ASP.NET MVC Framework |
launched as a Community Technology Preview |
| 2008-03-05 |
ASP.NET MVC Preview 2 |
released |
| 2008-05-01 |
ASP.NET MVC Preview 3 |
released |
| 2008-07-16 |
ASP.NET MVC Preview 4 |
released[3] |
| 2008-08-28 |
ASP.NET MVC Preview 5 |
released[4] |
| 2008-10-16 |
ASP.NET MVC Beta |
released[5] |
| 2009-01-27 |
ASP.NET MVC RC |
released[6] |
| 2009-03-03 |
ASP.NET MVC RC2 |
released[7] |
| 2009-03-17 |
ASP.NET MVC 1.0 |
released[8] |
| 2009-07-31 |
ASP.NET MVC 2.0 Preview 1 |
released[9] |
| 2009-11-17 |
ASP.NET MVC 2.0 Beta |
released[10] (compatible with VS2008SP1, not VS2010Beta/RC) |
| 2009-12-17 |
ASP.NET MVC 2.0 RC |
released[11] (compatible with VS2008SP1, not VS2010Beta/RC) |
| 2010-02-05 |
ASP.NET MVC 2.0 RC2 |
released[12] (compatible with VS2008SP1, not VS2010Beta/RC) |
View Engines
The mainstream view engine used in the ASP.NET MVC Framework is the Web Forms view engine, which ships with the framework itself. By default, the view engine in the MVC framework uses regular .aspx pages to design the layout of the user interface pages onto which the data is composed. However, different view engines can be used.[13] Additionally, rather than the default ASP.NET postback model, any interactions are routed to the controllers using the ASP.NET 3.5 SP1 Routing mechanism. Views can be mapped to REST-friendly URLs.[1]
Other view engines:
- The MVCContrib library contains 8 alternate view engines. Brail, NDjango, NHaml, NVelocity, SharpTiles, Spark, StringTemplate and XSLT.
- The StringTemplate View Engine utilizes a .NET port of the popular Java Templating engine, StringTemplate.
- Spark is a view engine for the ASP.NET MVC (and the Castle Project MonoRail) frameworks.
References
External links
