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,
I need to see the version column as well and that isn't visible in the screen shot. Please attach this so I may review.
On closer inspection of the screenshots, there are a few differences:
On VS 2013 the following additional assemblies are loaded that are not loaded on VS 2012:
On VS 2012 there is three instances of the Infragistics2.Shared.v10.3.dll being loaded. My expectation is that one loaded from the installation folder will be a different version than the other one. The version column should confirm this. This is the assembly that SubObjectBase is defined in and that is the constraint on the generic where you are seeing the error.
Once you verify that the extra version of the assembly is being loaded the next step will be to look into why. Once we find that we can correct the issue on your machine. For this you should look at the references in the project and you may also want to look at hint paths for assemblies in the references as well as reference paths for your project.
Let me know if you have any questions.
These are the reference to Shared-DLL on the Machine with VS 2012.
One thing that stands out as being unusual is that the references from the VS 2012 machine are being loaded from the ProjectAssemblies folder in your local AppData which is unusual. This folder appears to be a temporary location for storing assemblies. Please do a clean and rebuild of your project using Visual Studio 2012 and see if this impacts the behavior for where the assemblies are loaded and the error that you get in the designer.
Let me know if you have any questions with this matter.
Hello Alan,
i solved the Problem. Solved means, that i have a solution, but no Explanation...
Please watch the next five posts, i've illustrated the solution...
Greetings and thank you for your patience, Karsten.
the assemblys in the different directories are the same, no one is corrupted or signed.
Anyway, it works now, I'm satisfied.
Thank you and have a nice weekend,
Karsten Heimer.
I am not sure I have an explanation unless the assembly in the reference path is different in some way such as maybe it is the one that is signed by a verisign certificate while the other one isn't. Maybe the assembly in that location was corrupted in some way.
Picture 5 of 5
Picture 4 of 5
Picture 3 of 5