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

Free Support Forum - aspose.com

Creating .pdf-files with Aspose.words for .Net


we are creating a component using Aspose.Words for .Net

The component takes as it’s input an xml-file containing data and an Microsoft Office Word 2013 word template file (.dotx).

It uses the input to build a new Word document (.docx) file, which is then saved as a .pdf-file.

(We actually just save the document built with format .docx and .pdf).

We have noticed an error when Aspose saves the .pdf-file.

If we take the .docx file that our component outputs and

1) Open this file in Microsoft Office Word

2) Save it with format .pdf.

We get a different result than if we do this with Aspose!

Attached you’ll find a .zip-file with the input file:


And two output-files:

Populated_header_mansave.pdf (which is the .pdf file manually saved with Word)

TestNewPDF.pdf (which is the .pdf file saved by Aspose.word).

The simple c#-code used to save the second output file is a console application with the following code:

using System;

using System.Collections.Generic;

using System.Linq;

using System.Text;

using System.Threading.Tasks;

using Aspose.Words;

namespace testAspose


class Program


static void Main(string[] args)


Aspose.Words.License license = new License();


Aspose.Words.Document d = new Document(@“C:\Users\jacobs\Documents\word2xmltest\Output\Populated_header.docx”);

d.Save(@“C:\Users\jacobs\Documents\word2xmltest\Output\TestNewPDF.pdf”, Aspose.Words.Saving.SaveOptions.CreateSaveOptions(SaveFormat.Pdf));




Is there an error in Aspose.Word ?

Hi Jacob,

Thanks for your inquiry. We tested the scenario and have managed to reproduce the same problem on our end. For the sake of correction, we have logged this problem in our issue tracking system as WORDSNET-12475. Our product team will further look into the details of this problem and we will keep you updated on the status of correction. We apologize for your inconvenience.

Best regards,

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

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