I get the following error in the upgrade log when i try to upgrade a Visual studio project.
12:06:19: web.config has been backed up.
12:06:19: Updating LatonClient.csproj...
12:06:19: LatonClient.csproj has been backed up.
12:06:19: No matching assembly located in available assemblies Infragistics2.Win.UltraWinCalcManager.v10.1.FormulaBuilder
12:06:19: at Infragistics.VersionUtilitySupport.Core.ProductAssemblies.AssemblyList.AssemblyNameChange(String assemblyName, Int32 versionLocation, XmlNamespaceManager xmlNamespaceManager, String& assemblyNameNoVersion, Boolean ignoreErrors)
at Infragistics.VersionUtilitySupport.Core.ProductAssemblies.AssemblyList.FindNewAssemblyNode(String assemblyName)
at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.FetchNewAssemblyNode(String assemblyOldName)
at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.Upgrade(String rootDirectory)
I am trying to upgrade to 2010 Volume 2
Hello Donor,
Is there any specific reason you're trying to access an assembly in the Infragistics2.Win namespace from a web project?
Here is a listing of the files contained in the 2.5.2 build folder. It effectively contains sql script files, webservices, some DLL's and a client installation for that specific version...
Something worth noting is that I now have a load of newly created backup folders. In some releases the is and associated website and several webservices. It looks like the version utility has found their related web.configs and backed them up..... look at the dates for the C:\projects\LatonClient\Builds\2.5.2\CommonUnitsWS\backup folder below....
Directory of C:\projects\LatonClient\Builds\2.5.2\2.5.2 Scripts
03/12/2009 12:56 <DIR> .
03/12/2009 12:56 <DIR> ..
03/12/2009 20:15 232,309 CommonUnits.sql
02/12/2009 13:35 434,684 Latons.sql
02/12/2009 12:46 59,578 Latons2.5.1.sql
03/12/2009 20:01 40,190 Latons2.5.2.sql
02/12/2009 15:29 133,946 Tuds.sql
03/12/2009 18:44 437,060 Tuds1.0.sql
6 File(s) 1,337,767 bytes
Directory of C:\projects\LatonClient\Builds\2.5.2\CommonUnitsWS
21/06/2010 12:15 <DIR> .
21/06/2010 12:15 <DIR> ..
21/06/2010 12:15 <DIR> backup
04/12/2009 16:06 <DIR> bin
04/12/2009 09:20 49 PrecompiledApp.config
13/07/2010 17:18 8,778 web.config
04/12/2009 16:06 <DIR> WebServices
2 File(s) 8,827 bytes
Directory of C:\projects\LatonClient\Builds\2.5.2\CommonUnitsWS\backup
13/07/2010 17:15 8,778 web.config.bkp
1 File(s) 8,778 bytes
Directory of C:\projects\LatonClient\Builds\2.5.2\CommonUnitsWS\bin
04/12/2009 16:06 <DIR> .
04/12/2009 16:06 <DIR> ..
04/12/2009 09:20 160 App_Code.compiled
04/12/2009 09:20 69,632 App_Code.dll
2 File(s) 69,792 bytes
Directory of C:\projects\LatonClient\Builds\2.5.2\CommonUnitsWS\WebServices
03/12/2009 20:15 104 CIL.AdminWS.asmx
03/12/2009 20:15 1,733 CIL.AdminWS.asmx.resx
03/12/2009 20:15 113 CIL.StandardWS.asmx
03/12/2009 20:15 1,733 CIL.StandardWS.asmx.resx
4 File(s) 3,683 bytes
Directory of C:\projects\LatonClient\Builds\2.5.2\GAC
03/12/2009 13:03 <DIR> .
03/12/2009 13:03 <DIR> ..
04/12/2009 09:20 472,064 CIL.Admin.dll
03/12/2009 11:01 1,020,416 CIL.Laton.dll
04/12/2009 09:20 83,968 CIL.Standard.dll
04/12/2009 08:59 363,008 CIL.Tuds.dll
4 File(s) 1,939,456 bytes
Directory of C:\projects\LatonClient\Builds\2.5.2\LatonClient
03/12/2009 12:51 <DIR> .
03/12/2009 12:51 <DIR> ..
04/12/2009 10:24 11,278,848 Local Aids Setup.msi
04/12/2009 10:24 485,888 setup.exe
2 File(s) 11,764,736 bytes
Hello Raymond,
I consulted with the engineer who wrote the Version Upgrade Utility, and he said that there must be something in one of your solution or project files that refers to something in the Builds folder. He said that the Version Upgrade Utility only looks at the solution and project files when determining the files to upgrade.
Dave,
for what its worth i created a brand new project and solution with a single form and one infragistics control on it. I ran the version upgrade sucessfully....
i copied the builds folder from the other project to this new project and the version upgrade fails. This project can have absolutely no links to the builds folder as it only has one form with one control..
R
Hello,
How are you passing the solution to the Version Upgrade Utility? If you're passing in a solution or project file, then the Builds folder should be ignored by the Version Upgrade Utility. However, if you're passing in a WebSite, then the utility crawls the folder looking for items to upgrade.
I firstly tried the solution option and when that didn't work i tried the project option. I have never selected the website option
no, as there are historical builds of the application at a point in time...
Do you want the Version Upgrade Utility to upgrade the web.config files in the Builds folder that reference our assemblies?
I have logged this as an issue with our development team.
Because of the way the Version Upgrade Utility is designed, your best solution is to move the "Builds" folder out of the solution folder when you upgrade the project. The utility looks through the folder tree for any web.config files and that's what's causing the issue.
You can send an email to support@infragistics.com. Make sure you include "CAS-48066-VCR31K" in the subject.