Good day All,
I am having trouble upgrading our solution (previously .NET 4.0 using SR 2077 of Volume 13.2, using VS 2013) to .NET 4.5.1 and the 4.5 Infragistics libraries. When I use the version utility tool it tells me there is nothing to upgrade. The log file looks as follows:
01:16:03: Gathering volume and assembly information.01:16:03: Gathering volume and assembly information.01:16:04: Analyzing CallCentreMgrWeb.csproj...01:16:04: The project has references that need to be updated.01:16:04: Could not load the project. Please see the Log file for more details.01:16:04: Root element is missing.01:16:05: at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.ParseDocumentContent() at System.Xml.XmlTextReaderImpl.Read() at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace) at System.Xml.XmlDocument.Load(XmlReader reader) at System.Xml.XmlDocument.Load(TextReader txtReader) at Infragistics.VersionUtilitySupport.Core.File.Types.DataSourceFile..ctor(String path, FileBase owner) at Infragistics.VersionUtilitySupport.Core.File.Types.AdditionalFiles.AddFile(String fileName, List`1 listOfAssemblies) at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.CheckProjectForAdditionalFiles(Boolean isSLProject, XmlNode node) at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.Analyze()
Am I doing something wrong?
Hello Eduard,Thank you for posting in the community!
You could find detailed information regarding the use of VersionUtility at:Web_Using_Version_Upgrade_Utility Please notice, there are a couple of pre-requirements in order to successfully use the VersionUtility, and the last two seem relevant to your case.
Before You Start pre-requirementsBefore upgrading your content, be sure to consider the following:
-If you are moving your solution from one version of Visual Studio to another, the Visual Studio upgrade should be done before using the utility. The supported versions for the Visual Studio are 2008 and above and the utility can upgrade the Infragistics ASP.NET versions 2005 and later.-If you are upgrading the .Net version of your projects, you should perform it before using the Version Utility-Before executing the version utility you should ensure that the files in the solution are not marked read-only. If the files are under source control you should check them out before launching the utility.
So if you are using TFS, please make sure all files on the solution are checked out before attempting to upgrade, so they are read/write.
I have also attached a screenshot in order to illustrate the settings required to upgrade to CLR 4.5.1. Please notice I have also included version 13.2 to be upgraded to and it is only to demonstrate the option to choose specific Infragistics product as well as the CLR version. The ASP.NET Options section depends on the project upgraded and in general you could not go wrong enabling these checkmarks.
If the issue persists and you find it time consuming, you could also try to manually change the assembly references. It is possible there is some project specific issue causing this exception. From the stack trace I can see that the project is missing the root element and without your project I cannot investigate further why this happens. Try to change the versions manually and if the same error still exist it would be helpful if you are able to attach to the case a project that reproduces this.
Please let me know how these suggestions work for you!
Good day Ivaylo,
I did all the above (not the manual update though), but I did run the upgrade tool again this morning (the latest one, the previous stack trace was from the 13.1 tool), and found this extra line:
"Could not locate registry entry Software\Microsoft\.NETCore\v4.5\AssemblyFoldersEx where we look for installed products."
I did try the upgrade tool when setting the framework to both v4.5 and v4.5.1, but no joy either way.
I'll go through the process of manually updating the references on Monday if the above information does not help in finding the problem.
You could try to run the Version Utility alone without loading the project and select the appropriate option to upgrade Solution/Project/ or Website. Then specify the required path in the file system. Using the VersionUtility this way could do the trick.
If the issue persists, could you please provide a CodeSample reproducing this, so I can test it on my side? It will be greatly appreciated as I was unable to reproduce this scenario. I have created a private case CAS-136670-Z7H5G8, so you could attach the code sample there, and not expose it to the public.
I'll have a look at your suggestion when I can, I have other priorities at the moment.
I'll let you know.
Thank you for letting us know about this.
Meanwhile if you have other questions or concerns regarding this issue, do not hesitate to contact us again.