Hello Rob Hudson,

When sending in examples for using try and catch is not be good practice to send without providing code on how the exception is being handled in the catch block. The main reason is because it makes it difficult to debug and knowing whether an exception has been thrown. Most likely it would not be necessary to add try and catch blocks because the targeted application type would simply provide information about the exception details to the user.

As far as the usage of "Tasks.Parallel.ForEach" function my knowledge is limited in this area and also threading. It would be best for our engineers to take a look at the sample provided using a console application type when using the Infragistics.Documents.Excel library because it is not required to use in the ASP.NET platform.

Let me know if you have any questions with this matter. Thank you.

I understand.  I don't need to make a decision on this today, just sometime in the next week or so.

Also, one thing I didn't mention, but something your engineers might want to look at... 

When I populate the Worksheet using the Tasks.Parallel.ForEach loop, it will occassionally throw an "object no found" error trying to fill the cell.  That is why it is in a "try-catch" clause.  So after export, there are a handfull of cells that didn't populate.  That's probably something they will want to fix...

Thanks, - Rob

Hello Rob Hudson,

This is just an update that I am currently working on an isolated sample using a console application type and also running the comparison on my local machine for the library provided in SpreadsheetGear and Infragistics.Documents.Excel.

I will send another update to the thread on my progress on mid-day tomorrow.

Let me know if you have any questions with this matter. Thank you.

Hello Rob Hudson,

Thanks for the update.

As far as improvements for the Workbook.Save functionality in our future release I would like to first demonstrate with a console application type. By the end of today I would like to at least provide a sample and a log for this to have our engineers take a look at this specifically.

Let me know if you have any questions with this matter. Thank you.

Thanks!

In your opinion, should I look for speed improvements in Workbook.Save in the next release?

I need something to tell my clients... If it is unlikely to be improved in the next release, I need to purchase another solution just for the exports.