I'm adding a tab control and have to manually add the child tabs. If I open the designer it then adds the tab yet again with a different assembly pathing name.
As in, I start with this (ending tags omitted for readability);
BorderStyle="Solid" BorderWidth="1px" ThreeDEffect="False">
<tabs>
<igtab:tab key="Buyer" text="Buyer"></igtab:tab>
After I open the designer I get;
I also get this when I initially add the control
<Infragistics.WebUI.UltraWebTab.Tab Key="Buyer" Text="Buyer"></Infragistics.WebUI.UltraWebTab.Tab>
Anyone got any ideas?
Yes, this type of problem may occur if for some reason the design-time assembly of the control (named Infragistics35.WebUI.UltraWebTab.v8.2.Design) is not correctly referenced from the global assembly cache.
Is there anything special in your setup, for example, have you explicitly added a reference to this assembly in your project, and is it located in your /bin folder? I believe in this case you will need to remove it from there - the design time assemblies need to be in the GAC (c:\windows\assembly) only.
Also, any additional information will surely provide further clues (e.g. which versions are you using, do you have different versions of the IG controls installed on your development machine, are you using version mapping using bindingRedirect, etc)
Nope, no added references, no DLLs in the bin, etc....
After the re-install I just dumped the pages section in the web.config and made sure there were no binding redirects in there.
Thanks
I am also following the other forum thread you have on this topic with Devin Rader, and I guess everything is fine now. Thanks for sharing how you got it working - this will surely be helpful for other developers.
I have only seen this type of problem reported two times for almost an year and both times bindingRedirect was mentioned, so I will investigate what is going on there, hopefully something useful will pop up.
Thanks again.