Its not recommended but it does work! We managed to get MS Office to kick out around 10-15 documents per second on a single IIS server running ASP.net without much optimization. If you wanted to go crazy you could just load-balance the servers and kick out way more docs.
We tried to use a Java lib for Office docs but it was a pain in the neck. We had some very specific requirements for embedding an ActiveX control into a document and the OSS libs just weren't going to cut it. If your volume requirements aren't too high, I would just start with interoping with MS Office.
Comments
I know of a lib for Python but it only produces xls.
http://sourceforge.net/projects/pyexcelerator
If you are using ASP.NET why can't you install Office on the server?
The latest (licensed) version of Office we have is 2003. As far as we know using Office 2003 for server side Excel generation is not recommended.
Thanks for the link to the Python framework though.
Its not recommended but it does work! We managed to get MS Office to kick out around 10-15 documents per second on a single IIS server running ASP.net without much optimization. If you wanted to go crazy you could just load-balance the servers and kick out way more docs.
We tried to use a Java lib for Office docs but it was a pain in the neck. We had some very specific requirements for embedding an ActiveX control into a document and the OSS libs just weren't going to cut it. If your volume requirements aren't too high, I would just start with interoping with MS Office.
Yes - COM Automation stuff is generally not recommended for non-interactive usage. Although I think many people do get away with it.