Hi,
I created a small sample project based on your code. My grid actually has 15 columns (with a variety of data type) and 200,000 rows. And I am able to run the application and export the grid to Excel successful with no Exceptions.
Please try my sample and see if the exception occurs with my sample.
If you get the same exception with my sample (and I don't) then that would indicate this is an issue with the versions of the Infragistics or other assemblies on your machine. I am testing with our latest internal build so if it works fine for me and not you, I recommend that you try getting the latest service release and see if that fixes the problem.
If you do not get the exception with my sample, then it means something else in your application is causing this. Perhaps you are using a particular data type of some feature of the grid that I am not. So we would need to narrow that down.
Also, if you can, I recommend trying this with fewer rows, just as a test to see if the number of rows is relevant to the issue. It takes a long time to export so many rows, and testing and debugging will go a lot faster if you can reduce the time it takes to test.
Finally, I'd be interested to know if the location to which you are saving matters. The Temp folder might be protected by Windows, so you might try saving somewhere else, like to a non-system folder and see if that makes a difference.
Hi Mike
We are still busy tracing the error, in the meantime could you please supply a link to the following Service Release downloads:
Infragistics_WindowsForms_16.1_ServiceRelease_2033.zip and
Infragistics_WPF_16.1_ServiceRelease_2056.zip
Hello,
Please find the links you requested below:
Please let me know if I can further assist you.
I did a little more research and this error message does not appear to be related to the UltraGridExcelExporter directly. It seems to be an issue with the DotNet framework and the ZIP packaging.
I found a couple of articles that might help. The articles seem to indicate that this error message is related to either the application domain identity and/or permissions. And it only happens with very large files (which makes sense since you are exporting such a large number of rows and columns).
Since no other customers have reported this issue, and plenty of people are exporting very large grids, my guess is that you are doing something unusual with your AppDomain or permissions and that's causing the issue.
Here's a couple of links I found that may help you track down the issue or work around it:
https://connect.microsoft.com/SQLServer/feedback/details/764356/subscription-fails-due-to-error-system-io-isolatedstorage-isolatedstorageexception-unable-to-determine-the-identity-of-domain
http://stackoverflow.com/questions/7488442/epplus-2-9-0-1-throws-system-io-isolatedstorage-isolatedstorageexception-when-tr
Thanks for the articles.
The application is quite complex and is part of an Office Com AddIn, resulting in the UltraGrid export happening deep inside many nested levels of containership.
We used our data in the sample project that you provided and the export ran without errors. In this regard, simplistic "Hello World" type of projects generally do not stress the AppDomain sufficiently to flush out all weaknesses.
We will pursue this issue further, maybe trying to move the export higher up the containership chain, and will report back any sollutions
Thanks for your efforts thus far.
Best Regards