ASP.NET Core has since been released, which unified ASP.NET, ASP.NET MVC, ASP.NET Web API, and ASP.NET Web Pages (a platform using only Razor pages). MVC 6 was abandoned due to Core and is not expected to be released. Core is currently planned to merge into ".NET 5".[4]
Based on ASP.NET, ASP.NET MVC allows software developers to build a web application as a composition of three roles: Model, View and Controller.
The MVC model defines web applications with 3 logic layers:
Model (business layer)
View (display layer)
Controller (input control)
A model represents the state of a particular aspect 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 information.[7]
"ASP.NET MVC framework is a lightweight,[9] highly testable presentation framework that is integrated with existing ASP.NET features. Some of these integrated features are master pages and membership-based authentication. The MVC framework is defined in the System.Web.Mvc assembly."[10]
The ASP.NET MVC framework couples the models, views, and controllers using interface-based contracts, thereby allowing each component to be tested independently.[citation needed]
Apache License 2.0 release
In March 2012, Scott Guthrie announced on his blog that Microsoft had released part of its web stack (including ASP.NET MVC, Razor and Web API) under an open source license (Apache License 2.0).[11]
Guthrie wrote that "Doing so will enable a more open development model where everyone in the community will be able to engage and provide feedback on code checkins, bug-fixes, new feature development, and build and test the products on a daily basis using the most up-to-date version of the source code and tests."
The source code now resides on CodePlex. ASP.NET Web Forms was not included in this initiative for various reasons.[12]
The view engines used in the ASP.NET MVC 3 and MVC 4 frameworks are Razor and the Web Forms.[29][30] Both view engines are part of the MVC 3 framework. By default, the view engine in the MVC framework uses Razor .cshtml and .vbhtml, or Web Forms .aspx pages to design the layout of the user interface pages onto which the data is composed. However, different view engines can be used.[31] Additionally, rather than the default ASP.NET Web Forms postback model, any interactions are routed to the controllers using the ASP.NET Routing mechanism. Views can be mapped to different URLs.[7]
Other view engines:
The MVCContrib library contains 8 alternate view engines. Brail, NDjango, NHaml, NVelocity, SharpTiles, Spark, StringTemplate and XSLT.[32]
The StringTemplate View Engine utilizes a .NET port of the Java templating engine, StringTemplate.[33]
Spark is a view engine for the ASP.NET MVC (and the Castle Project MonoRail) frameworks.[34]
NDjango is a port of the Django web framework's templating language to .NET. It is written in F# and comes with Visual Studio extension including full Intellisense support.[35]
Jon Galloway, Phil Haack, Brad Wilson, and K. Scott Allen, Professional ASP.NET MVC 3, Wrox, 2011, ISBN1-118-07658-3
Jeffrey Palermo, Jimmy Bogard, Eric Hexter, Matthew Hinze, and Jeremy Skinner, ASP.NET MVC 4 in Action, Manning Publications, 2012, ISBN978-1617-29041-1
Steven Sanderson, Adam Freeman, Pro ASP.NET MVC 3 Framework, Second Edition, Apress, 2011, ISBN1-4302-3404-0
Jonathan McCracken, Test-Drive ASP.NET MVC, Pragmatic Bookshelf, 2010, ISBN1-934356-53-0
Stephen Walther, ASP.NET MVC Framework Unleashed, Sam's, 2009, ISBN0-672-32998-0