Hi:
I have an isssue with my word automation on server side. This application is developed using C#. Microsoft recommend not to use word automation on the server side. I am looking for an alternative. Can I use Aspose .word to do that. I have word document stored as WORDML (microsoft version on XML) in a SQL server table. In my server side code I want to convert that to word document and store it in a file location. Then I sent the word document as an attachment to a fax server.
I am looking for soem thing like below
********SAMPLE CODE NOT ACTUAL********
//Read the WordML document
WordDocument doc;
//Utility class for loading Word ML into DOM
WordMLtoDocIOConverter converter = new WordMLtoDocIOConverter();
doc = (WordDocument)converter.Convert(@"../../Data/Template.xml");
//Save the document in Binary Format
doc.Save("Sample.doc",FormatType.Doc);
Can Aspose.word do this. Please let me know.
Govindan
Yes, Aspose.Words supports full-fledged WordML to DOC conversion. You cannot load WordML from file or stream and save it to a binary DOC format.
You can download our evaluation pack and test it for yourself. But please mind that evaluation version truncates the document to app. 200 paragraphs and also inserts evaluation watermark in generated documents. To get a fully functional Aspose.Words for one-month of evaluation testing please follow the instructions described here:
https://docs.aspose.com/words/net/licensing/
Hi:
It looks really great. I hope aspose.word perform very well in a multi-threaded server environment(it look like it). I tested it with lot of different wordprocessingML and Aspose.Word not only converted them to doc with out any error but also completed the convertion much much faster (amazing!!!). We are buying this product right away. I hope you have a phone technical support.
Microsoft has listed issues with word automation in server under the following article
They should include your name in the list too. Good Luck.
Thank you
Govindan
Thank you very much. As a person responsible for WordML in Aspose.Words I was especially pleased to read all your kind words about this feature. We have put a lot of effort into it, and, speaking of WordML in particular, no other product can boast the same level of WordML implementation. We are second only to MS Word.
We have phone support, but it is dealing mainly with purchase and licensing issues. All technical problems are best to be addressed directly to developers and this forum is the fastest way of reaching them. We usually answer technical requests within 12 hours and fix most of them in hotfixes which are released every 3-4 weeks.
Speaking of the MS list, yes, I have seen it. Maybe sometime we will appear in this list too 
Best regards,
Vladimir Averkin
Developer/Technical Support
Aspose Auckland team
Hi:
I have a digital signature added in the word ML and it is not getting converted.When I open up with regular Word 2003, it has the signature. Word automation also converts it with out any issue. When I use Aspose.word, very thing else looks cool except the digital signature.
Govindan
Please attach the document that displays this problem. I will check it up and fix it if it is a bug…
Hi:
Please attached is the document giving us trouble. The signature is not converted in our out put from Aspose.
Govindan
713 544 5773
Strange, when I open the attached document in MS Word 2003 it does not show any digital signatures warning. It normally should as you digital signature is obviously not included in trusted list on my computer.
I have also checked the presence of digital signature using Tools | Options | Security | Digital Signatures menu dialog in Ms Word 2003 and it shows an empty list.
Also, digital signature in WordML are contained inside Base64 encoded binary data inside w:docSuppData element and your document does not even have such an element.
So by all signs the document you have attached does not have any digital signatures. Please check if you have attached the correct document.
Best regards,
Vladimir Averkin
Developer/Technical Support
Aspose Auckland team
Hi Vladimir:
Please opne the document using word 2003 and you will see the following signature (It is an image)
But when converted using aspose.word, i miss this signature which has to go with the document.
Please clarify or tell me how to include the above in my document.
Thank you
Govindan
Hi:
Actually it is a jpeg image attached above teh signature. Can word.aspose convert jpeg image.
Please let me know
Govindan
If you mean the image of the scanned signature appearing below XXXXXXXXX, Inc. then it is converted properly with Aspose.Words. I can send you the converted document where the signature is present.
Hi :
I am using 4.2.2.0 Aspose.Word. Do I have to use some other version. When I convert using Aspose.word, I do not see it. Do I have to install any special font.
Thank you
Govindan
You are using the latest version and no special fonts are required. Please attach the converted document in DOC format that you are getting, I would like to check it.
Hi:
This is a confidential file. Could you please give your email address. I will send it to you.
Thank you
Govindan
But you have already attached the initial file. Sorry, I don’t understand why you don’t want to attach the same file converted to DOC.
Hi:
I know it is confusing.
The file I posted do not have all the actual details. The actual document will have my company logo and names. When I have both my company logo and the bottom signature, the conversion doesn’t work . When I remove my company logo and keep the signature image alone, it is working. That is what really confuses me. So I have to send you the whole actual file. I hope you got my point.
Govindan
Got your point. I have sent my e-mail to you.
Hi:
Did you get my email with attachment. Any progress??
Govindan
Yes, I have researched your file. Here is a brief description of the problem.
The file looks like a regular WordML document generated by MS Word 2003. But the signature image looks like it was inserted using some other tool. Several signs point to it. The most important is that the place where it is inserted is inappropriate and does not conform with official WordprocessingML schema. The w:pict element containing the image is inserted inside w:t element, whereas it should be inserted inside w:r element, which is an upper level container for elements like w:pict and w:t.
However, MS Word is able to read it due to some peculiar feature that I have discovered by extensive testing. I have found that despite what schema says, MS Word is able to read w:pict elements from anywhere in the document. You can place w:pict element just anywhere in the document, inside any element, even outside w:body element, even inside font or document properties declaration - still MS Word will read it and display when file is opened. That is probably some side effect of MS Word WordML parser design. Aspose.Words parser is not designed in this way. It expects to find certain elements only where they could occur according to schema.
Now, I need to decide how to deal with this problem. Whether I should redesign our parser so that it could read w:pict from anywhere in this document. But that will complicate the existing code and will impact the speed. Also, I am not convinced that this is actually necessary as right now we see only one minor particular problem. Namely, that w:pict element is occuring inside the w:t element which is conflicts with WordML schema, but MS Word is able to handle it, wheras Aspose.Words cannot. So, I am reluctant to do any major parser redesign now.
Second possible solution is to modify parser to be able to deal with this specific problem only, i.e. make it expect w:pict element inside w:t element. That is possible and can be done fast.
Third option is to ask you to check how the signature image is inserted inside the WordMl file in such an inappropriate place and if it can be fixed on your side.
So right now I think the best way is to ask you about the third option and if it is not possible - then go with the second option.
What will you say?
Hi Vladimir:
Good analysis. Let me try the 3rd option and get back to you soon.
Thank you
Govindan