I can't seem to upgrade my project to 2011.1. Following is the log file:
11:10:30: Gathering volume and assembly information.11:10:37: ProjectFile element: SOS_SalesPlanner\SOS_SalesPlanner.vbproj is being treated as a proj file.11:10:37: Analyzing SOS_SalesPlanner.vbproj...11:10:37: The following project needs to have its references updated: 11:10:50: Gathering volume and assembly information.11:10:52: ProjectFile element: SOS_SalesPlanner\SOS_SalesPlanner.vbproj is being treated as a proj file.11:10:52: Analyzing SOS_SalesPlanner.vbproj...11:10:52: The following project needs to have its references updated: 11:10:55: Upgrading Solution SOS_SalesPlanner.sln11:10:55: Updating SOS_SalesPlanner.vbproj...11:10:55: C:\Projects\SOS_SalesPlanner\SOS_SalesPlanner\SOS_SalesPlanner.vbproj has been backed up.11:10:55: Object reference not set to an instance of an object.11:10:55: at Infragistics.VersionUtilitySupport.Core.File.Utilities.ProductUtilities.GetAssemblyName(String str) at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.Upgrade(String rootDirectory)
I have tried to use the Upgrade addin as well. Different error but still does not work.
11:16:38: Gathering volume and assembly information.11:16:39: ProjectFile element: SOS_SalesPlanner\SOS_SalesPlanner.vbproj is being treated as a proj file.11:16:39: Analyzing SOS_SalesPlanner.vbproj...11:16:39: The following project needs to have its references updated: 11:16:43: Index was out of range. Must be non-negative and less than the size of the collection.Parameter name: index11:16:43: at System.ThrowHelper.ThrowArgumentOutOfRangeException() at Infragistics.VersionUtilitySupport.Core.ProductAssemblies.Products.KeepLatestVolumes(List`1 installedNetAdvantageProducts) at Infragistics.VersionUtilitySupport.Core.ProductAssemblies.Products.TrimList() at Infragistics.VersionUtilitySupport.Core.SourceChanger.Upgrade()
Project is currently 2010.3. No source control. I have tried other projects and they seem to go without a problem so this must be project specific. So I guess it is something with this one solution, but I don't have any idea what is causing the problem????
Dan
Ok I got it to upgrade. I had to go into the My Project folder and maually delete the contents of the Licenses.licx file. And then it worked. Could not just delete the file. Had to empty it with a text editor, and then it worked.
Not sure if this a bug or not. When I drilled into the "list of things to do" emptying the Licenses file was one of the things that it needed to do...
Hi Dan,I have tried the same. But it doesn't seem to be working. I have the same problem as you pointed out.
Saravanan
You probably need to post your log file here and your .PROJ file as well. That way they can help you figure out what is wrong.
I delete the content of licenses.licx but continue de error
09:34:40: Gathering volume and assembly information.
09:34:57: ProjectFile element: Sicov\Sicov.vbproj is being treated as a proj file.
09:34:57: Analyzing Sicov.vbproj...
09:34:57: The following project needs to have its references updated:
09:35:00: ProjectFile element: Cuentas x Pagar\Cuentas x Pagar.vbproj is being treated as a proj file.
09:35:00: Analyzing Cuentas x Pagar.vbproj...
09:35:00: The following project needs to have its references updated:
09:35:00: ProjectFile element: ReportServerSicov\ReportServerSicov.rptproj is being treated as a proj file.
09:35:00: Analyzing ReportServerSicov.rptproj...
09:35:00: Nothing for us to upgrade.
09:35:00: ProjectFile element: ReportesCliente\ReportesCliente.vbproj is being treated as a proj file.
09:35:00: Analyzing ReportesCliente.vbproj...
09:35:00: ProjectFile element: smo\VS\SMODemos\SMODemos.csproj is being treated as a proj file.
09:35:00: Analyzing SMODemos.csproj...
09:35:00: ProjectFile element: Instalador\Instalador.vdproj is being treated as a proj file.
09:35:00: The project file C:\Users\Erick\Desktop\SuCasa 2010\Instalador\Instalador.vdproj doesn't appear to be in Xml or is malformed.
09:35:03: Upgrading Solution Sicov.sln
09:35:03: Updating Sicov.vbproj...
09:35:03: C:\Users\Erick\Desktop\SuCasa 2010\Sicov\Sicov.vbproj has been backed up.
09:35:03: Updating Infragistics2.Shared.v10.3 to new reference Infragistics2.Shared.v11.1.
09:35:03:
09:35:03: Updating Infragistics2.Win.AppStylistSupport.v10.3 to new reference Infragistics2.Win.AppStylistSupport.v11.1.
09:35:03: Updating Infragistics2.Win.Misc.v10.3 to new reference Infragistics2.Win.Misc.v11.1.
09:35:03: Updating Infragistics2.Win.SupportDialogs.v10.3 to new reference Infragistics2.Win.SupportDialogs.v11.1.
09:35:03: No matching assembly located in available assemblies Infragistics2.Win.UltraGauge.v10.3.Design
09:35:03: at Infragistics.VersionUtilitySupport.Core.ProductAssemblies.AssemblyXmlFile.GetNewAssemblyNameBecauseOfNameChangedBetweenVolumes(String assemblyName, Int32 indexOfVolumePortionOfAssemblyName, XmlNamespaceManager xmlNamespaceManager, Boolean ignoreErrors)
at Infragistics.VersionUtilitySupport.Core.ProductAssemblies.AssemblyXmlFile.LocateNewAssembliesNodeforCurrentAssembly(String assemblyName)
at Infragistics.VersionUtilitySupport.Core.File.Types.ProjectFile.Upgrade(String rootDirectory)
We have released and SR for the Version Utility today for 2011.1, and you can read more about it at http://blogs.infragistics.com/blogs/engineering/archive/2011/08/22/2011-1-version-utility-installer-re-release-service-release.aspx
Thanks!!!!!
This solution working perfectly after remove the unused references
Sorry to hear that. Are you using the Version Utility Extension in Visual Studio? If so, try the Stand-alone Version Utility; there is a bug on x64 machines where you get this error, and we are working on fix it currently, but it's just in the Visual Studio extensions.
I removed the Gauge reference and Design reference, but still not working.
01:05:16: Gathering volume and assembly information.
01:05:18: ProjectFile element: Sicov\Sicov.vbproj is being treated as a proj file.
01:05:18: Analyzing Sicov.vbproj...
01:05:18: The following project needs to have its references updated:
01:05:21: ProjectFile element: Cuentas x Pagar\Cuentas x Pagar.vbproj is being treated as a proj file.
01:05:21: Analyzing Cuentas x Pagar.vbproj...
01:05:21: The following project needs to have its references updated:
01:05:21: ProjectFile element: ReportServerSicov\ReportServerSicov.rptproj is being treated as a proj file.
01:05:21: Analyzing ReportServerSicov.rptproj...
01:05:21: Nothing for us to upgrade.
01:05:21: ProjectFile element: ReportesCliente\ReportesCliente.vbproj is being treated as a proj file.
01:05:21: Analyzing ReportesCliente.vbproj...
01:05:21: ProjectFile element: smo\VS\SMODemos\SMODemos.csproj is being treated as a proj file.
01:05:21: Analyzing SMODemos.csproj...
01:05:21: ProjectFile element: Instalador\Instalador.vdproj is being treated as a proj file.
01:05:21: The project file C:\Users\Erick\Desktop\SuCasa 2010\Instalador\Instalador.vdproj doesn't appear to be in Xml or is malformed.
01:05:25: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
01:05:25: at System.ThrowHelper.ThrowArgumentOutOfRangeException()
at Infragistics.VersionUtilitySupport.Core.ProductAssemblies.Products.KeepLatestVolumes(List`1 installedNetAdvantageProducts)
at Infragistics.VersionUtilitySupport.Core.ProductAssemblies.Products.TrimList()
at Infragistics.VersionUtilitySupport.Core.SourceChanger.Upgrade()
Remove the reference to the Design assembly for Gauge. The tool doesn't handle upgrading design references as we don't recommend having Design assemblies referenced in a project. That said older versions of Gauge as well as Chart would add references to there design assemblies. You should be able to remove it, and upgrade without issue.