The ASP.NET MVC Framework uses a Model-view-controller pattern. Microsoft added this framework to 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 table. A Controller handles interactions and updates the model to reflect a change in state of the application. A View extracts necessary information from a model and renders a user interface to display that.
In April 2009, the ASP.NET MVC source code was released under the Microsoft Public License (MS-PL).
The ASP.NET MVC Framework couples the models, views, and controllers using interface-based contracts, thereby allowing each component to be easily tested independently. 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 (for example, you can create a View Engine based on XSLT files). 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.
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
2008-08-28 ASP.NET MVC Preview 5 released
2008-10-16 ASP.NET MVC Beta released
2009-01-27 ASP.NET MVC RC released
2009-03-03 ASP.NET MVC RC 2 released
2009-03-17 ASP.NET MVC 1.0 released
2009-07-31 ASP.NET MVC 2.0 Preview 1 released
View Engines
The mainstream view engine used in the ASP.NET MVC Framework is the WebForms view engine, which ships with the framework itself.
Other view engines:
The MVCContrib library contains 4 alternate view engines. Brail, NHaml, NVelocity, 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.
|
No responses found. Be the first to respond and make money from revenue sharing program.
|