I inherited a web application we're doing in ASP.NET 2.0 and a consultant put in a few Infragistic controls so far using v6.3. I want to rip them out and use the same controls but v.7.2. So I removed all the assemblies for 6.3 in the projects (and lines in the web.config relating to 6.3), added the 7.2 assemblies and when I compile, I get the following GAC conflicts:
Error 32 The type 'Infragistics.WebUI.UltraWebNavigator.WebTreeNodeEventArgs' exists in both 'c:\WINDOWS\assembly\GAC_MSIL\Infragistics2.WebUI.UltraWebNavigator.v7.2\7.2.20072.61__7dd5c3163f2cd0cb\Infragistics2.WebUI.UltraWebNavigator.v7.2.dll' and 'c:\WINDOWS\assembly\GAC_MSIL\Infragistics2.WebUI.UltraWebNavigator.v6.3\6.3.20063.53__7dd5c3163f2cd0cb\Infragistics2.WebUI.UltraWebNavigator.v6.3.dll' C:\tfs\xxxBSD Process Tool\xxx\Controls\LocationSelector.ascx.cs 59 107 C:\...\
and a few others for some other types of Infragistic web controls.
So I have 2 questions
1) How to resolve this issue so that it picks up the 7.2 controls instead. Do I have to re-drag in the controls from the 7.2 toolbox and delete the controls in mark-up or should this just work?
2) Can you run 2 versions of Infragistics on your PC. Can you use 2 versions of Infragistics in your web app?
Hello,
Thanks for writing. You can have any number of different versions of our controls on the same machine, installed in the GAC (in fact, this is one of the main reasons we use the GAC).
The problem you have is most probably related to the fact the Visual Studio.NET silently adds a new line in web.config for each assembly you reference. However, when you remove the reference, it does not remove the line from web.config and still searches for that assembly, hence the problem you are having when removing 6.3 and then adding 7.2
Could you please open your web.config file and search for any references to Infragistics 6.3 assemblies, and if there are some, just delete them? Also, you may try running the "6.3" search for the whole solution to see if you have them referenced somewhere explicitly in ASPX files - you will also need to remove them from there in that case.
Please, let me know if this helps.
My fault, I missed a couple in the web.config ;) and also some assembly references in an .ascx that consultant had in there. Works fine now.