Where can I find the samples that you are referring to?  The samples in NetAdvantage 2009.1 do not include the "Excel 2007 Custom Packaging" sample that you are referring to.

Regards,

David

Hi,

I've just integrated the sample to generate MS Excel 2007 file with CLR2.0 and Infragistics 2009.1

The xlsx file is generated, but excel exporter seems to limit to number of exported rows to 65k as if it was an old xls file : if FileLimitBehaviour is Throw exception, I get an exception. If it is truck the rows are trunked to 65K.

Any idea ?

Thanks

Hi dialogues,

we're trying to use Infragistics Excel assembly on CLR 2.0 to open an Excel 2007 spreadsheet. But Workbook.Load method requires an IPackageFactory object.

How did you get integrating the sample to generate Excel 2007 on CLR 2.0? Please can you kindly send me some suggestions? 

Thanks in advance, bye! Valentina

If you are using CLR 2, then you will need to supply an IPackageFactory, as CLR2 does not have built-in packaging support. There may be some third-party component you can buy to do the packaging for you. But personally, I'd recommend updating to CLR3 if you can - it will be a lot easier.

Duplicate

Hi Mike Saltzman,

I couldn't get your point. What i have understood so far is, in order to export rows that greater than 66K to Excel 2007 using CLR 2.0, we need IPackageFactory.  I downloaded the solution(Excel 2007 Custom Packaging CS) but still i am not able to run. I could not build windowsbase.dll using .Net 2.0. Could you please advise on how to use IPackageFactory with 2.0?

I am not saying that some third party component should implement the interface.

In order to create a file compatible with Excel 2007 format, the file has to be packaged. CLR 3 provides built-in packaging functionality, so if you are using CLR3, the Infragistics Excel assemblies can utilize this in order to create Excel files for you.

But if you are using CLR2, then there is no support for packaging. Therefore, the Infragistics components cannot create an Excel file.

So.. in order to allow you the possibility of creating an Excel file in CLR2, the Excel assembly exposes an interface that you can implement so that you can do the packaging yourself. You could, theoretically, write your own packaging routines to packages the files. Or, you could use some other 3rd-party packaging utility.

Then, when the interface is called to package the file, you could handle the packaging however you want since the Infragistics components are unable to do it.

The sample provided is a sample of how to use the interface. Once again, since there is no support in the CLR2 framework to package the files, and the sample can't reply on any third-party software, it uses the CLR3 packaging functionality for demonstration purposes. All it's intended to demonstrate is that when the interface methods are called, it's up to you to package or un-package the files.

Hi Mike,

I really don't understand why a third-party utility should implement an Infragistics-defined interface... There's no documentation available on what the implementing object should do... If you provide a method to load an Excel document, what should the object do?

Dialogues, I can tell you for sure that on a pure .NET 2.0 environment the Infragistics sample won't work. So the best choice is to deploy WindowsBase.dll with your application (but it sound really strange, since - you're right - it's a part of the framework...).

Bye, Valentina

There's no way Infragistics can supply an example of implementing your own IPackageFactory in any real way, because it would require some third-party packaging utility. So the sample that is included demonstrates using an IPackageFactory with the packaging support built-in to CLR3. It uses CLR3 because the same can only demonstrate implementing the interface, not the actual packaging. So if you intend to implement your own packaging, you either need a third-party packaging utility or you have to write your own packaging routines to package the data in a way that is compatible with Excel.