I upgraded a project from 10.3 to 11.1 using the version utility, in my references I don't have any visible 10.3 references and all the .licx files contain references to 11.1 (I went back and deleted the contents of all 11.1); however, I get this error after deploying my application to the end user:
Could not load file or assembly 'Infragistics2.Win.UltraWinGrid.v10.3, Version=10.3.20103.2094, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
When I run the compiled version on my end, when I go to our About Box I can see that the code is still referencing the 10.3 version; even though, I upgraded the solution (and projects) to the latest release of 11.1.x.x and there are no direct references to 10.3
I decided to remove the data grid from the form and drag the new grid and set the properties. This seems to have fixed my issue. This was a bizarre situation. I wonder if it has anything to do with:
a) I have many versions still installed on my dev. machine: 2009.2 through 2011.2
b) The change to the version utility, it used to work better before now every service release I have to run the version updater to get my project on the latest installed up.
I could not visibly see a reference to 10.3 anywhere. If anyone runs into this issue, remove the control and then put a new copy on the form.
When I upgraded another project (that targets .Net Framework 2.0), I'm seeing references to 11.1 even though I ran the Upgrade Version Utility.
Hello Pete,
If for some reason you are still seein this behavior and a message that your application still tries to refer an older version, what I could suggest is to verify if you have having any user controls, that are used. If so, could you please remove them from the Toolbox, and try to recreate them using the latest version available. If you are using any custom build assemblies, please try to rebuild them against the latest version.
Other thing that you could try is removing your "bin" and "obj" folders if you are not storing any kind of sensitive information and rebuild one more time your app.
If it still referencing an older version we could create a LogMeIn session so I will be able to look close what is happening at your end.
If you have any other questions please feel free to ask.
I'll give it go and let you know.
If you have any new information about this behavior, I would be glad to take a look at it.
If you need any other assistance please do not hesitate to ask.
Thank you for letting me know.I will be waiting for your results.