We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Open XML SDK comparison

Hello,

I would like to know what's the differences between generating Word document with the Open XML SDK and generation Word with Aspose ?!

What are benefits of the Aspose method ?

In my case, Word DOCX format is only the wanted format and the only functionnality that currently makes me choose Aspose is the pdf conversion.

Thanks


This message was posted using Aspose.Live 2 Forum

Hi

Thanks for your request.

1. Aspose.Words and Open XML SDK have the similar DOM. However, in Aspose.Words you can use DocumentBuilder that simplifies creating documents from scratch. For instance here is a simple code to generate “Hello word” document using XML SDK and Aspose.Words:

[XML SDK]

public void HelloWorld(string docName)

{

// Create a Wordprocessing document.

using (WordprocessingDocument package = WordprocessingDocument.Create(docName, WordprocessingDocumentType.Document))

{

// Add a new main document part.

package.AddMainDocumentPart();

// Create the Document DOM.

package.MainDocumentPart.Document =

new Document(

new Body(

new Paragraph(

new Run(

new Text("Hello World!")))));

// Save changes to the main document part.

package.MainDocumentPart.Document.Save();

}

}

[Aspose.Words]

Document doc = new Document();

DocumentBuilder builder = new DocumentBuilder(doc);

builder.Write("Hello World!!!");

doc.Save(@"out.docx");

2. Aspose.Words supports a wide set of documents formats:

http://www.aspose.com/documentation/.net-components/aspose.words-for-.net/file-formats-and-conversions.html

So, if it will be required to export or import your documents in other format than DOCX, you will be able to easily achieve this using Aspose.Words. No changes in the document generation process will be required.

3. Aspose.Words provides a very powerful and flexible reporting engine. You can execute simple Mail Merge using Aspose.Words (as you can do in MS Word):

http://www.aspose.com/documentation/.net-components/aspose.words-for-.net/simple-mail-merge-explained.html

In additional, you can execute Mail Merge with Regions to fill tabular data for example:

http://www.aspose.com/documentation/.net-components/aspose.words-for-.net/mail-merge-with-regions-explained.html

4. Unlike, XML SDK, using Aspose.Words you can render your document into various formats, like PDF, XPS, SWF or image. In addition, you can print documents or convert them to series of Images.

http://www.aspose.com/documentation/.net-components/aspose.words-for-.net/rendering-and-printing.html

5. Also, Aspose provides 24x7 support in our forums. So you will get answer shortly in case of any issues.

http://www.aspose.com/documentation/.net-components/aspose.words-for-.net/technical-support.html

Please let me know if you need more information. We will be glad to help you.

Best regards,

Well, you've answered your question yourself - rendering to PDF.

Then Adam added a few more useful facts.

From the top of my head I can add the following:

1. Document assembly. You can join documents or copy fragments from one document to another and Aspose.Words will do all the work of merging styles and list formatting properly.

2. Search and replace. Try searching for richly formatted text in the SDK, for example "HelloWorld". It will not find because "hello" and "world" will be in different nodes in XML, whereas Aspose.Words makes it easy.

3. Field Update! How could I forget. Assemble documents programmatically and insert a TOC field and update it exactly like MS Word does. That's a job for Aspose.Words.

4. Range-like operations e.g. Bookmarks["BMK1"].Text = "new text". Try that in SDK and let us know how easy is that.

There some write up here http://www.aspose.com/documentation/.net-components/aspose.words-for-.net/wordprocessingml-docx-xml.html

And thanks for the idea, we will definitely elaborate on this and add a topic to our documentation.

And of course availability on different platforms: .NET, Java, some use it on Mono.

The issues you have found earlier (filed as WORDSNET-4403) have been fixed in this .NET update and in this Java update.


This message was posted using Notification2Forum from Downloads module by aspose.notifier.