The only requirement for this tool is the availability of .NET Framework 4 on the machine. You do not need to have Visual Studio or ASP.NET MVC installed (if you don’t want to open your project!). Even though the tool performs an automatic backup of your solution, it is recommended that you also make a manual backup of your solution.
To convert an ASP.NET MVC 2 project developed in Visual Studio 2010 to an ASP.NET MVC 3 project in Visual Studio 2010, complete these steps:
Run the converter
Choose a solution
Click “Convert”
To convert an ASP.NET MVC 2 project developed in Visual Studio 2008 to an ASP.NET MVC 2 project in Visual Studio 2010, complete these steps:
Open a project in Visual Studio 2010 to convert the solution and project files from VS2008 to VS2010
Upgrade the target version of the .NET Framework of each project to .NET Framework 4, because ASP.NET MVC 3 is compatible only with .NET Framework 4
Run the converter
Choose a solution
Click “Convert”
What can it do
Open ASP.NET MVC 2 projects from Visual Studio 2010 (no other versions of ASP.NET MVC, or Visual Studio are supported)
Create a full backup of your solution folder
For every VB or C # project that has links to System.Web.Mvc.dll it will be (it includes both ASP.NET MVC web application projects and ASP.NET MVC test projects):
Update links to ASP.NET MVC 2
For each VB or C # ASP.NET MVC Web application, it will be:
Change project type to ASP.NET MVC 3
Update links in the root ~ / web.config to ASP.NET MVC 3
Update ~ / web.config root to have a coherent redirect from ASP.NET MVC 2 to ASP.NET MVC 3
Update links in ~ / Views / web.config to ASP.NET MVC 3
Add or update JavaScript files (add jQuery, add jQuery.Validate, add Microsoft AJAX, add / update Microsoft MVC AJAX, add Microsoft MVC Validation adapter)
Unknown project types or project types that have no relation to ASP.NET MVC will not be updated.
What it can't do
it cannot convert projects made in Visual Studio 2008 or in the .NET Framework 3.5.
he may have problems if your solution contains projects that are not located in the solution catalog.
if you are using a source control system, it may have problems overwriting files. It is recommended that before converting, you check all files for the presence of a source control system.
it cannot change the code in the application, which may need to be changed due to breakdown of the conversion between ASP.NET MVC 2 and ASP.NET MVC 3.
release notes include a step-by-step conversion guide for your application.