There are several problems with the new upgrade utility in NetAdvantage 10.2.

1. When trying to upgrade a solution, the utility seems to be recursively checking every file in every sub-folder for the read-only attribute (even if the files are not used in the solution).  Why is it checking files that are not used in the solution?  Workaround for this:  right-click the top-level folder and remove the read-only flag recursively on all files.

2. The utility still would not upgrade my solution.  Then, I started trying to upgrade each project individually (one at a time).  During this process, some of the projects in the solution would show the message "Analyzing <project name>.csproj...   Nothing for us to upgrade" when analyzing the project.  That is fine, but it appears that the utility was failing when upgrading the solution because it encountered a project that had "nothing to upgrade".  It should just ignore project with nothing to upgrade, so the whole solution can be upgraded to save time.

3.  One our solutions, contains a project (web application) that references both CLR 2.0 (in Win Forms) and CLR 3.5 (in Web) Infragistics files.  This project would fail the upgrade and had to be upgraded manually in the project file, the aspx files, and the ascx files.  The web.config file was the only file that was updated by the utility.  The previous version of the upgrade utility handled upgrading this project with no problem.

4. Another feature in the previous version of the upgrade utility that made things easier was the ability to select multiple project files and update them all at once (instead of one at a time).  We have over 100+ projects to upgrade.  Please add that feature back to this new version update utility.

Hope that this information helps others going through the upgrade process...