This is a copy of original post Version-Free assemblies - Infragistics.Excel fatal problem posted in Windows Forms » Forums » NetAdvantage for Windows Forms » Configuration and Deployment but there nobody cares (23 items in last 6 months, only 4 with verified answer, 7 posts still with ZERO replies) , so I try it here again.
In the documentation (see the link bellow) there is written, that:"For assemblies with both CLR2 and CLR 3 versions (like Infragistics2.Excel.v10.2 and Infragistics3.Excel.v10.2), the version -free assemblies will match the latest CLR version. So the version-free Excel assembly will be Infragistics.Excel.dll and is the one built for the CLR3 version."
http://help.infragistics.com/Help/NetAdvantage/WinForms/2010.3/CLR2.0/html/Introduction_About_Version-Free_Assemblies.html
But this is not true:
In the directory Version-Free (20102_WinForms_VersionFree.zip) there is usedInfragistics.Excel.dll in zip file which is built on the CLR2 and not on CLR3. (same as Infragistics2.Excel.v10.2.dll)
In the directory Version-Free - Signed(20102_WinForms_VersionFree_Signed.zip) there is used Infragistics.Excel.dll which is built on the CLR2 and not on CLR3 too.
Infragistics.Win.UltraWinGrid.ExcelExport.dll has a same problem.
And our problem is that when we try to export an excel file in format for Office 2007, we receive an error
"packageFactory cannot be null. When saving to Excel2007 workbook format and using the Infragistics2.Excel assembly, you must provide an IPackageFactory to handle the packaging of data. If you are using the DotNet Framework 3.0 or higher, use the Infragistics3.Excel assembly instead, and the packaging will be handled by the WindowsBase class"
But there are not version-free CLR3 versions of those dll-s.
Can somebody help me with that.
I check the size of "dll" in last service release and it looks OK. Checked in version 10.2.
I copy an answer into the original post too.
Thanks.
Hello.
Have you downloaded, installed, and tested the service release?
I posted about the service release prematurely. This issue has been logged with the development team and it will be available in the next service release. Please let me know if you have any questions.