When I try to upgrade it fails cause it cannot find the 9.2 version of the assembly, I uninstalled 9.2 then installed 10.3 so no the 9.2 version is no longer available. This utility requires both versions to be installed???

09:06:07: Gathering volume and assembly information.
09:06:31: Analyzing Analyzer.vbproj...
09:06:31: The following project needs to have its references updated:
09:06:47: Gathering volume and assembly information.
09:06:47: Analyzing Analyzer.vbproj...
09:06:47: The following project needs to have its references updated:
09:06:49: Updating Analyzer.vbproj...
09:06:49: C:\Maple\Src\Managed Applications\BA\Analyzer\Analyzer.vbproj has been backed up.
09:06:49: No matching assembly located in available assemblies Infragistics2.Shared.v9.2
09:06:49:    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)

SelectionControl is the parent

TestControl is under the SelectionControl folder and contains a reference to the SelectionControl project.

I attempted to upgrade SelectionControl project in the SelectionControl folder and was not successful.

Here's what I'm getting:

11:58:04: Gathering volume and assembly information.
11:58:16: App.config appears to be read-only or not accessible for some reason.

This project is a DLL and contains no App.Config. However the TestControl project is and EXE and does contain App.Config. Why is the utility even looking into the TestControl folder??

The read-only check is a recursive check, which starts at the provided project directory (in your case the SelectionControl folder), and will check all files in all the child directories (including your TestControl directory). This is done because we don't know at the time of this check what files in which directories we may need to access, so we check all files in the project directory to make sure no one is read-only to avoid issue later in the upgrade process.

I understand but you should treat this as a warning and allow the upgrade attempt. If your explaination is correct the upgrade will be successful. As it is now you cannot upgrade due to the verification failure.

It appears the scenario you are trying to do isn't supported right now with the utility as it wants access to all files we could possible modify in it's working folder.  Unfortunately, if we throw a warning, which would fix your case, it would cause issues later for people that we should have thrown the error for.  We'll see if we can improve this checking to narrow it down better in the future to handle your scenario.

Just FYI. The old project upgrade utility had no problem with the structure we use for some of our projects. Thank you for taking the time to look into this matter.

Thank you. is what we are looking for more

Hello,

I have encountered a similar problem.

I wanted to migrate from 9.1 (Infragistics2.WebUi.xxxxxxx.v9.1) to 10.3 clr 4.0 (Infragistics4.WebUI.xxxxx.V10.3). It gave me the error 'No matching assembly located in available assemblies Infragistics2.WebUI........'

Then I first upgraded the references (with the version utility tool) to 10.3 CLR 2.0. This was successfull.

The next step I took was upgrading the 10.3 CLR 2.0 version to 10.3 CLR 4.0. This succeeded also.

PS: I used the control assemblies path option.

Kind regards,

Erik

Hello,

I encounter the same error by upgrading an ASP.NET application from Infragistics 10.3 CLR 2 to CLR4 on Windows 7:

02:48:57: Updating Infragistics2.WebUI.Shared.v10.3 to new reference Infragistics4.WebUI.Shared.v10.3. -> Seems to work!

02:48:57: No matching assembly located in available assemblies Infragistics2.WebUI.UltraWebGrid.v10.3 -> Doesn't work!

Any ideas for me?

Regards

Hi,

In order to support more and new scenarios the upgrade utility tool had to be changed. If with older upgrade utility tool you have not encountered the same issue with project structure, you can use it as you specify the version to which you would want to upgrade.

Let me know if this works for you or you have any questions.

Regards,

Stefaniya