Author Archives: Romank

Some customers have reported they cannot build an application with Aspose.Words in Microsoft Visual Studio 2010 RC.

We confirm you cannot build a project if you select one of the following Target framework settings in the Project Properties:

• .NET Framework 3.5 Client Profile
• .NET Framework 4.0 Client Profile

The error message is “… it has a dependency on Sysem.Web … which is not in the currently targeted framework”.

Yes, Aspose.Words has a dependency on System.Web to provide a … Continue Reading

Great new features:

• Table of Contents (TOC) fields are now updated/rebuilt.
• Load and save Word 2010 OOXML documents (ISO 29500 Transitional).
• Improvements to handling embedded OLE objects and OOXML packages.
• TrueType fonts are subsetted and embedded into output EPUB.
• Footnotes are partially supported when rendering/saving to PDF.

A useful new article in the documentation with details of features supported in save to PDF http://www.aspose.com/documentation/.net-components/aspose.words-for-.net-and-java/save-in-the-adobe-portable-document-pdf-format.html.

To download http://www.aspose.com/community/files/51/.net-components/aspose.words-for-.net/default.aspx

Expect more posts from the senior developers on the Aspose.Words team about what they’ve done … Continue Reading

As of today we have three OOXML versions/flavours:

• OOXML ECMA-376 1st Edition, 2006 (this is Word 2007) – as of today, Aspose.Words supports only this.

• ISO/IEC 29500:2008 Transitional (Word 2010) – we have code ready for the upcoming release that will support this.

• ISO/IEC 29500:2008 Strict – Aspose.Words will support this some time in the future.

The question I have to all of the customers of Aspose.Words is:

What is the best way to represent the different OOXML versions in the Aspose.Words … Continue Reading

http://twitter.com/AsposeWords

Let’s have some fun. Will really tell you what’s happening.… Continue Reading

If a Microsoft Word document was opened/saved or converted by an Aspose.Words version earlier than today’s Aspose.Words for .NET 8.2.1, it could exhibit the following problems:

• Document.Open, Document.New etc macros will no longer fire.

• VBA project digital signature might be lost.

• Macros Window could show no macros.

• Custom toolbars and customizations to standard toolbars could be lost.

• Keyboard command customizations could be lost.

All of the above has now been resolved. Aspose.Words now fully preserves and converts all of the … Continue Reading

We are delighted to announce the availability of Aspose.Words for SharePoint, which is our latest addition to the Aspose.Words product family.

This release, Aspose.Words for SharePoint 1.0 makes high quality document conversions for DOC/DOCX/ODT/RTF/PDF/XPS and others easily accessible to SharePoint users.

Aspose.Words for SharePoint is built on top of the world-class Aspose.Words for .NET document processing technology and makes it available as an easy to deploy and use functionality in Windows SharePoint Services or Microsoft Office SharePoint Server environments.

A Bit … Continue Reading

You already know that Aspose.Words can convert DOC, DOCX, ODT, etc to PDF very well, but you might be wondering can it convert it the other way around?

The answer is yes. But you need to use our specialized and “experimental” product Aspose.Recognition for .NET. It can convert PDF to any document format supported by Aspose.Words, that are DOC, DOCX, ODT, MHTML, and others.

If you are interested, Aspose.Recognition internally consists of a PDF parsing module, an artificial intelligence … Continue Reading

You might be wondering, Aspose.Words for .NET 7.0 is barely 2 months old and we already have 8.0, a major version change? Yes, and that change reflects the importance of one feature that we have finally added.

You now can just design a template document like this:

MERGEFIELD TableStart:Orders
…
    MERGEFIELD TableStart:OrderDetails
    …
    MERGEFIELD TableEnd:OrderDetails
MERGEFIELD TableEnd:Orders

and then call

doc.MailMerge.ExecuteWithRegions(myDataSet); <br>

and Aspose.Words will do its magic to produce an order document. Then you can of course

doc.Save(myStream, SaveFormat.Pdf);<br>

etc.

Aspose.Words’ … Continue Reading

Many customers have requested the following features over time:

1. Make sure Aspose.Words does not lose mail merge data source settings in a document during open/save or conversion.
2. Ability to specify a mail merge data source for a document programmatically.
3. Ability to query or clear mail merge settings specified in a document.

We are happy to tell that we have implemented this. We have added the Document.MailMergeSettings property and MailMergeSettings, Odso, OdsoFieldMapData, OdsoRecipientData classes.

The current plan is … Continue Reading