After going through all my solutions and upgrading from 18.2 to 20.1 and having the Version Utility tell me that all my upgrades were successful, I later find that NONE of my projects were upgraded. I then noticed this in the analysis when trying again.
Expanding the project says "Could not load the project. Please see the Log file for more details" LOG details are below
Why didn't the utility alert me of this instead of making it seem like everything was good to go?
Here is what's in the log. Yes, there is no MVC5 folder on my machine. Why is that? Where does it come from?
Could not find directory C:\Program Files (x86)\Infragistics\2014.2\Ignite UI\MVC\MVC5\Bin\ to search for Infragistics assemblies.
Hello Sam,
The Version Utility creates a log file under Documents\Infragistics\Tools\Version Utility. Can you please provide the log file, so I can investigate the issue further?
ThanksVasil
08:30:46: Running User Interface Version 20.1.20201.108:30:46: Gathering volume and assembly information.08:30:46: Could not find directory C:\Program Files (x86)\Infragistics\2014.2\Ignite UI\MVC\MVC5\Bin\ to search for Infragistics assemblies.08:32:13: ProjectFile element: SchedulePlanner.csproj is being treated as a proj file.08:32:13: Analyzing SchedulePlanner.csproj...08:32:13: The project has references that need to be updated.08:32:30: Could not load the project. Please see the Log file for more details.08:32:30: Object reference not set to an instance of an object.08:32:30: at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.CheckProjectForAdditionalFiles(Boolean isSLProject, XmlNode node) at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.Analyze()08:32:30: ProjectFile element: ..\..\..\AppLibs\SchedulePlanner\BusinessObjects\NG.TMS.AppLibs.SchedulePlanner.BusinessObjects.csproj is being treated as a proj file.08:32:30: Analyzing NG.TMS.AppLibs.SchedulePlanner.BusinessObjects.csproj...08:32:30: Nothing for us to upgrade.08:32:59: Could not load the project. Please see the Log file for more details.08:32:59: Object reference not set to an instance of an object.08:32:59: at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.CheckProjectForAdditionalFiles(Boolean isSLProject, XmlNode node) at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.Analyze()08:32:59: ProjectFile element: ..\..\..\AppLibs\SchedulePlanner\DataAccess\NG.TMS.AppLibs.SchedulePlanner.DataAccess.csproj is being treated as a proj file.08:32:59: Analyzing NG.TMS.AppLibs.SchedulePlanner.DataAccess.csproj...08:32:59: Nothing for us to upgrade.08:33:00: Could not load the project. Please see the Log file for more details.08:33:00: Object reference not set to an instance of an object.08:33:00: at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.CheckProjectForAdditionalFiles(Boolean isSLProject, XmlNode node) at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.Analyze()08:33:00: ProjectFile element: ..\..\..\AppLibs\SchedulePlanner\Interfaces\NG.TMS.AppLibs.SchedulePlanner.Interfaces.csproj is being treated as a proj file.08:33:00: Analyzing NG.TMS.AppLibs.SchedulePlanner.Interfaces.csproj...08:33:00: Nothing for us to upgrade.08:33:00: Could not load the project. Please see the Log file for more details.08:33:00: Object reference not set to an instance of an object.08:33:00: at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.CheckProjectForAdditionalFiles(Boolean isSLProject, XmlNode node) at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.Analyze()08:33:00: ProjectFile element: ..\..\..\AppLibs\SchedulePlanner\BusinessLogic\NG.TMS.AppLibs.SchedulePlanner.BusinessLogic.csproj is being treated as a proj file.08:33:00: Analyzing NG.TMS.AppLibs.SchedulePlanner.BusinessLogic.csproj...08:33:00: Nothing for us to upgrade.08:33:00: Could not load the project. Please see the Log file for more details.08:33:00: Object reference not set to an instance of an object.08:33:00: at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.CheckProjectForAdditionalFiles(Boolean isSLProject, XmlNode node) at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.Analyze()08:33:00: ProjectFile element: ..\..\..\AppLibs\SchedulePlanner\BuildStub\BuildStub.csproj is being treated as a proj file.08:33:00: Analyzing BuildStub.csproj...08:33:00: Nothing for us to upgrade.08:33:01: ProjectFile element: ..\..\..\AppLibs\SchedulePlanner\ApplicationLogic\NG.TMS.AppLibs.SchedulePlanner.ApplicationLogic.csproj is being treated as a proj file.08:33:01: Analyzing NG.TMS.AppLibs.SchedulePlanner.ApplicationLogic.csproj...08:33:01: Nothing for us to upgrade.08:33:01: Could not load the project. Please see the Log file for more details.08:33:01: Object reference not set to an instance of an object.08:33:01: at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.CheckProjectForAdditionalFiles(Boolean isSLProject, XmlNode node) at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.Analyze()
I am glad that you were able to upgrade your projects.
Thank you for your feedback for the Version Utility. You are right that it should not show the upgrade as successful, when it was not able to load a project and nothing was upgraded. We will take a look at that and work on improving the tool.
Let me know if you need any additional help.
RegardsVasil
I ended up writing my own utility to upgrade my projects. I have hundreds of projects across several solutions, so doing it manually was not an option.
Someone needs to seriously look into the Infragistics Version Utility. Like I mentioned in a previous post, the issues have been present for over a decade. The logs are not helpful, and the user interface reports invalid results (says it completed successfully when it has not).
Thank you for the provided information. I see from the log file that only SchedulePlanner.csproj has some Infragistics references that need to be updated, but the version utility was unable to load the project. Instead of trying to upgrade the solution, can you please try to upgrade just this project with the version utility?Please also check if you have any references to design assemblies in your project and remove them if you have. If the upgrade is still not successful, please manually update the assemblies to 20.1. After that if you see errors "need v18.2 which is not installed", check your licenses.licx file. It may contain references to the old version of assemblies, so remove everything from the file and try to rebuild.Let me know how it goes.
By the way, these errors have been showing up on your forums for over 10 years, but they remain and the logs are not helpful.
https://ko.infragistics.com/community/forums/f/ultimate-ui-for-windows-forms/46595/error-upon-upgadation
Then there is the misleading message when the conversion is done.