Hi all,
Can anyone tell me what the general consensus is regarding using an Excel object in ASP.Net code? I have used it before in instances where the IIS server was dedicated to the specific app that produced Excel files for a small client load.
However I know there are various security and resource issues when .Net code on an IIS box is calling the Excel app and creating Excel files, and I have an app that will be on a more heavily used IIS box that will need to produce many Excel files for many users.
So the basic question is--when I have a web application with a requirement to produce and Excel file to be returned to the web client (either via download or opening the .xls from the server in a new tab), what are the best-practices for doing so?
I had considered creating .csv files instead, but the requirements include embedding functions and formatting so a .csv is not feasible.
Thanks,
--Jim
Can anyone tell me what the general consensus is regarding using an Excel object in ASP.Net code? I have used it before in instances where the IIS server was dedicated to the specific app that produced Excel files for a small client load.
However I know there are various security and resource issues when .Net code on an IIS box is calling the Excel app and creating Excel files, and I have an app that will be on a more heavily used IIS box that will need to produce many Excel files for many users.
So the basic question is--when I have a web application with a requirement to produce and Excel file to be returned to the web client (either via download or opening the .xls from the server in a new tab), what are the best-practices for doing so?
I had considered creating .csv files instead, but the requirements include embedding functions and formatting so a .csv is not feasible.
Thanks,
--Jim