Avoiding ASP.NET 2.0 Conversion Gotchas
One of my last few posts talked about a gotcha that occurs when converting web projects that had files that were no longer in the project file but still in the project folder.
After exchanging e-mails with Scott he pointed out a couple of things I thought were worth mentioning. First, in the RTM release (which just got uploaded to MSDN recently!) the migration wizard will list all the files found in the directory that were excluded or not part of the projects. You can find this in the ConversionReport.txt file.
The even better news is that an update to the migration wizard (based on all the latest feedback the ASP.NET team has received) is in the works. The updated version as I understand it will attempt to exclude those files by marking them as excluded in the converted folder. In case you haven’t seen in ASP.NET 2.0 Sites if you mark a file excluded it actually renames it by adding an excluded extension to the file. This is done because there is no longer a project file to maintain that information. It’s also important to understand that excluded files do get checked into source control.
The continuous improvement that has been seen in the migration wizard over the last year, and the fact that attention is still there to make it better is great!