Click here to Skip to main content
15,896,444 members

Comments by TheCoolCoder (Top 36 by date)

TheCoolCoder 5-Nov-12 0:46am View    
I thought so as you added a comment to the question and not reply, but wasnt sure if you disagreed with the whole idea..:-)..thanks..
TheCoolCoder 5-Nov-12 0:25am View    
Well there should be some reason or tons of reasons..That is all anyone can say unless you use the improve question link to update your question with scenario information and relevantcode snippets.
TheCoolCoder 5-Nov-12 0:19am View    
@SA : I dont completely understand your comment, what i pointed out was wrong? or is something else?? or is it directed at OP?
TheCoolCoder 5-Nov-12 0:04am View    
using COM Interop in a server environment is not supported by Microsoft. Also there are licensing issues related to using Office.Interop in a client-server environment. Refer this discussion.

The KB article Considerations for server-side Automation of Office does indeed say that you are licensed for server-side automation of Office products for use only if the clients are all licensed.

Just in case you are not aware of these.

If you want reliable/approved behaviour for your code Open XML SDK for Microsoft Office is the way to go with asp.net though only Office 2007 and later document formats are supported.
TheCoolCoder 26-Oct-12 0:09am View    
Take a look at the the updated solution.