In a lot of our Forms we will get this error, while trying opening the form in Visual Studio 2012. What is this?
Greetings, Karsten Heimer.
Hello Karsten,
I have never encountered this specific issue, but I did locate an old forum thread that appears to be the same issue. There were two different approaches to resolving the problem in the past.
The first approach that appeared to resolve the problem in the initial cases, dealt with making sure the referenced assemblies were correct. This was done by:
The second approach appeared to be related to using our version-less assemblies. In this scenario since there is no installer for the version-less assemblies, the customer deleted the previously installed assemblies from the GAC, and installed the version-less ones manually.
Hopefully one of these approaches will help you resolve the issue. Let me know of the outcome of these steps.
Thanks,
Chris
Hello Chris,
thank you für your answer.
I've checked all the Points in your post, except the version-less Option, but none of the changes works...
The version-less Option is not possible for me, because i do not have a single solution, i have 144 Solutions instead - the most of using Infragistics - and (based on bad design) there are all cross-referenced.
During my tests i found out, that the Problem only exists with Visual Studio 2012, not with Visual Studio 2013. Do you have an Explanation for that? Are there any known Bugs in Visual Studio 2012 related to this Problem?
Karsten,
My expectation is that the behavior for the same project would be consistent between Visual Studio 2012 and Visual Studio 2013. Are you loading the exact same project where this error happens?
In addition to removing the bin and obj directories and verifying the version is the same for all Infragistics references in the project, did you also verify that all dependent assemblies in the project are referencing the exact same version of the Infragistics assemblies as the project with the issue. You may also need to rebuild the dependent assemblies.
Let me know if I may be of further assistance.
Hello Alan,
i'm loading exact the same Project. The difference is the machine. VS 2013 is installed on another machine, but the Project ist the same (loaded via Network).
All Solutions using for her references the same Directory, wich contains all DLLs - own and third-Party like Infragistics, DevExpress or FarPoint. Therefore it is guaranteed, that all Solutions using the same Version (in our Dev-Environment exists only one Version).
Greetings, Karsten.
Are there different versions of our toolset installed on the two different machines? If there are references it is possible that additional assemblies would be loaded out of the GAC on one of the two machines and could account for the difference in behavior.