9 Answers, 1 is accepted
The only limitations in the library are related to limitations in the XLSX files which do not allow more than 1,048,576 rows by 16,384 columns in a single worksheet. I tested exporting a worksheet which contains 50 columns and 10,000 rows and on my machine, the file was generated for ~2 seconds.
Hope this information is helpful.
Thank you for your reply . I have one more query hope you will help me with this as well.
I want to write the file to Azure Blob Storage rather than creating it in file path. Is it possible? If yes can you help me with a sample?
You can pass a MemoryStream instance instead of the FileStream one so the content can be preserved in the MemoryStream. Once you are done with the generation, you can obtain the byte from the stream and save it according to your preferences.
RadSpreadStreamProcessing needs an object of type Stream to store the content of the document inside it. Indeed, the MemoryStream wouldn't be an efficient approach to keep the generated files inside when you expect such a big number of customers exporting large data simultaneously. What I can suggest you is to preserve files on the file system so the memory is not occupied and transfer these files when the application is not so busy.
Using a DataReader is possible but for the library there isn't a difference how the data will be set - the content is always written in the same way no matter how the data is obtained. The important thing here is that once the exporter for a row or cell is closed, the element is no more accessible.
Hope this is helpful
Do you have any code that you can share that demonstrates the solution ?