Migration Conversion Report Format
This topic describes the format of the migration conversion report that is created when you open a Microsoft Visual Studio .NET 2002 or 2003 project in Microsoft Visual Studio 2005. The Visual Studio Conversion Wizard makes many of the changes to your Web site to make it compatible with ASP.NET 2.0. The wizard is included in Visual Web Developer 2005, Visual Web Developer 2005 Express Edition, Visual Studio 2005, and Visual Studio 2005 Team System.
The conversion report starts with a title, which includes the name of the Visual Studio .NET 2002 or 2003 solution file. The title is followed by the date and time that the conversion took place.
During the conversion process, each Visual Studio .NET 2002 or 2003 solution file and project file is analyzed. Each solution or project file found results in one section in the conversion report. The solution section is shown first, followed by one project section for every project that is part of the solution.
Each section of the conversion report uses a table with four columns: Filename, Status, Errors, and Warnings. The Filename column contains the name of the project or solution file converted. The Status column contains Converted if the solution or project was converted; otherwise, it is blank. The Errors column is a count of errors during conversion and the Warnings column is a count of warnings during conversion.
Each row of the table is a notification, a warning, or an error message. Each row is expandable and can be opened to reveal more detailed information about the message.
Interpreting Report Messages
Notifications are generated to inform you of an action taken by the wizard. Notifications do not require any additional action to be taken.
Warnings are generated when the wizard takes an action, typically a modification to code or markup, that might cause a behavioral change in your Web application. Warnings should be reviewed but do not necessarily need to be acted on. The majority of warnings will require no further action by you. For example, the wizard generates a warning when the access level of code is changed, but this usually requires no further action.
Errors are generated when the wizard encounters code that cannot be automatically converted. Errors require you to address the problem to complete the migration. Errors generally will cause a compilation error if not addressed. If conversion report errors exist, you should focus your efforts on them. For help on troubleshooting errors, see.
Conversion Report Text Files
After you have closed both Microsoft Visual Studio 2005 and the conversion report that opens immediately after the wizard completes, you can still find the details of the conversion in the ConversionReport.txt file. This text file is in the root folder of the migrated project. It is not formatted in the same way as the XML conversion report viewed in Microsoft Visual Studio 2005, and contains more details about what was changed during the migration.