Hello,

I think that in your case you shouldn't use the following dll: Infragistics35.Web.v10.2.dll . Could you please remove it from your refferences and verify the behavior without it.

Please let me know if you have any further questions on this matter.

Hello,

I am not in agreement with you. Version 2009 vol 2 had no problem on the compatibility!. I have an application with a lot of code. I will not change anything because you decided to do otherwise and it would use other components to address the problem. Do you know the compatibility. I can not afford to change everything. I think it's a big problem.

Any solution for those of us who are using vb?

For the record, this is a big pain in the a@@ and infragistics needs to help us resolve this ASAP.  We have already lost a lot of development time on this.

We have had the same problem but unfortunately one of our projects has been written in VB and not C#, therefore you can't alias an assembly in the suggested way.

We have managed to grab the source code (provided as part of our licence) and recompiled Infragistics4.WebUI.UltraWebGrid.ExcelExport.v10.2.dll against Infragistics4.Web.v10.2.dll instead of Infragistics4.WebUI.Excel.v10.2.dll and this seems to work (although not ideal).

It would have been more practical if they removed the old excel assembly and told us to add the new one in it's place when using this release, instead of causing this type of upgrade nightmare... I wonder why it wasn't done in this way instead...

Hello All, 

First of all, I apologize for the inconvenience due to this change in 10.2, specially for VB project owners for which the suggested work-around didn't work. Just to give you an update, we have found a solution to the problem and will make the new exporters dependent upon the old library so that there are no namespace conflicts. 

We are currently testing the fix and are planning to release in the next SR. I will post an update with the date on which the fix will be available in public SR. If you need a private build, please contact support and they will be able to provide you with the private build sooner. 

If there are any queries or suggestions on the product, feel free to reach me directly at: murtazaa@infragistics.com

Regards, 

Taz. 

Hello,

In this case you are trying to refer to the different platform asseblies at the same time. The first one -

Infragistics35.WebUI.Documents.Excel.v11.1 belongs to the web ASP.NET platform, while the second one belongs to the Windows Forms platform.

Depends on your current needs and platform usage you should open the References of your project and remove the one that you don't need.

Please feel free to let us know if you have any other questions with this matter.

Has this problem been solved? I ask because I am getting a similar error with version 11 of the libraries:

The type 'Infragistics.Documents.Excel.Worksheet' exists in both 'c:\WINDOWS\assembly\GAC_MSIL\Infragistics35.WebUI.Documents.Excel.v11.1\11.1.20111.2064__7dd5c3163f2cd0cb\Infragistics35.WebUI.Documents.Excel.v11.1.dll' and 'c:\WINDOWS\assembly\GAC_MSIL\Infragistics3.Documents.Excel.v11.1\11.1.20111.2030__7dd5c3163f2cd0cb\Infragistics3.Documents.Excel.v11.1.dll'

Thanks Craig for verifying the issue and your continued patience. 

If there is anything else I can do for you, just let me know. 

Best Regards,

Taz.  

Hi Taz,

We have tested the 2010.2.2018 service release which resolves this issue and we have no further problems at this stage. Thank you to you and the rest of the team for the helping out with this problem.

Cheers!
Craig Wilson

Hi Taz,

Thanks for looking into this. Your solution sounds good and would atleast prevent conflicts in the same release, until a time when the older controls are removed for good.

Looking forward to the SR!

Cheers!
Craig Wilson