The Model-View-Controller architectural pattern continues to prove itself so invaluable at separating and decoupling domain concerns thirty years after its conception, that companies are still implementing it on top of their platforms. Microsoft originally released the Community Technological Preview of their MVC framework for ASP.NET at the end of 2007, and then in 2009 released the first version of it. A year later, in 2010, they released the second version, and that puts the third version on track to most likely be officially released in March 2011. They recently made the MVC 3 Release Candidate available, and it is backwards compatible with MVC version 1 and version 2, so developers can begin working on integrating the new features into existing MVC applications in preparation for the final release.
Several caveats about using the MVC version 3 ASP.NET framework Release Candidate exist. For one, it will not work on Windows XP machines. Also, if you have any previous Beta versions or CTP versions they must be uninstalled before installing the Release Candidate version. Other Beta or CTP releases for ASP.NET can also affect proper installation and should be uninstalled as well. And, while it is backwards compatible, it has been reported that creating a new MVC 3 project and moving all the old project files into the new project should help with other errors. The MVC 3 framework for ASP.NET looks to be a game-changer, especially with Razor integration. With the release candidate available for download and even production use, developers can start exploring the possibilities and updating legacy code in anticipation of the final official release.