Browse our Products

Aspose.Words for C++ 20.2 Release Notes

Major Features

We have added the following features from Aspose.Words for .NET on this regular monthly release:

  • Elliptic Curve Digital Signature Algorithm (ECDSA) is supported now
  • Encrypted documents are supported now

Limitations and API Differences

Aspose.Words for C++ has some differences as compared to its equivalent .NET version of the API. This section contains information about all such functionality that is not available in the current release. The missing features will be added in future releases.

  • The current release does not support some cryptography features - it cannot verify and sign documents.
  • The current release does not support downloading remote resources from the Internet.
  • The current release does not support the Metered license.
  • The current release does not support a multipage TIFF format.
  • The current release does not support LINQ and Reporting features.
  • The current release has limited support for database features - C++ does not have a common API for DB like .NET System.Data.
  • The current release only supports Microsoft Visual C++ version 2015 or higher and only for the x64 platform.

Full List of Issues Covering all Changes in this Release

WORDSCPP-904Add support for ECDSA signaturesNew Feature
WORDSNET-19750Add features to support field formats when FieldMergingArgs.Text is usedNew Feature
WORDSNET-19556Add feature to append VBA from one document to another using Document.AppendDocumentNew Feature
WORDSNET-18694Add feature to export w:colFirst and w:colLast properties of bookmarkStartNew Feature
WORDSCPP-737Add support for encrypted documentsBug
WORDSCPP-920Blank Page shows after Splitting the PageBug
WORDSCPP-931Loading DOC file throws FileCorruptedException exceptionBug
WORDSNET-19773Horizontal Line not Shown in Rendered DocumentBug
WORDSNET-18592After conversion to PDF, the content is not in the right placeBug
WORDSNET-11069Shape’s strikethrough issuesBug
WORDSNET-18733Chart Diagram rendered incorrectly in PDFBug
WORDSNET-19783System.NullReferenceException is thrown while saving the first page of the document to imageBug
WORDSNET-19800System.NullReferenceException is thrown while saving DOC to PDF/PNGBug
WORDSNET-19244Different table width between DOCX and ODTBug
WORDSNET-19461Gridlines and images are missing when saving into HTML with HtmlFixedSaveOptionsBug
WORDSNET-14251Table’s cells are lost after re-saving ODTBug
WORDSNET-19710Infinite loop during the call of Document.UpdatePageLayoutBug
WORDSNET-19712Footer Banner Repeats Multiple Times on all Pages in PDFBug
WORDSNET-19563Lettered Bullet Points aren’t preserved when converting from ODT to DOCXBug
WORDSNET-19257DOCX to PDF conversion issue with watermark renderingBug
WORDSNET-19900Unable to load shared library ’libSkiaSharp’ or one of its dependenciesBug
WORDSNET-19813System.NullReferenceException occurs upon calling UpdateFields after UpdatePageLayoutBug
WORDSNET-19814System.NullReferenceException occurs upon saving DOCX to PDF after calling UpdatePageLayout methodBug
WORDSNET-19129Document.Compare throws System.ArgumentOutOfRangeExceptionBug
WORDSNET-19600Order of fonts in the Font Substitution Table is incorrectBug
WORDSNET-19819System.NullReferenceException occurs upon calling UpdateFields after UpdatePageLayoutBug
WORDSNET-8967Clipping inline shapes by lineBug
WORDSNET-19227Table and Frame format is changed after saving .DOT as .ODTBug
WORDSNET-19727Footnote elements out of margins when saved to PDFBug
WORDSNET-19734Word to PDF tab alignment not workingBug
WORDSNET-19801Aspose.Words.FileCorruptedException is thrown while loading DOCBug
WORDSNET-19832FileCorruptedException is thrown while loading RTFBug
WORDSNET-19834Content shifted when saved to PDFBug
WORDSNET-19903Incorrect naming of Document.AutomaticallyUpdateSyles paramBug
WORDSNET-19414Inline image rendering orderBug
WORDSNET-19744System.IndexOutOfRangeException occurs upon DOCX to PDF ConversionBug
WORDSNET-19748Table Cell Shading Lost during RTF to PDF ConversionBug
WORDSNET-19749Watermark angle changes during DOCX conversionBug
WORDSNET-19803System.ArgumentOutOfRangeException is thrown while saving document’s pages to PNGBug
WORDSNET-19743System.NullReferenceException occurs upon saving DOCX to PDFBug
WORDSNET-19418Memory is not released upon conversion document with EMFBug
WORDSNET-19399Setting PreserveFormFields to true cancels the effect of UpdateSdtContentBug
WORDSNET-19916Reset StructureDocumentTag content formatting on comparisonBug
WORDSNET-19534Content in RTF is distortedBug
WORDSNET-19533Content in RTF is distortedBug
WORDSNET-19779Data labels are not rendered in PDFBug
WORDSNET-19782DOCX to PDF - hyphenation not sameBug
WORDSNET-19781System.InvalidCastException is thrown while comparing documentsBug
WORDSNET-19785Word to PDF dotted line problemBug
WORDSNET-19789Content pushed down from original position causing blank page at the end in PDFBug
WORDSNET-19795System.ArgumentOutOfRangeException occurs upon invoking Document.PageCountBug
WORDSNET-14708The content position is changed in output PDFBug
WORDSNET-14961Text is incorrectly positioned in RTL paragraphs inside auto-sized shapesBug
WORDSNET-15064DOCX  to PDF conversion issue with paragraph and shape positionBug
WORDSNET-14843DOCX to PDF conversion issue with image’s positionBug
WORDSNET-14826TextBox Shapes moved to next page during rendering to PDFBug
WORDSNET-18880The issue with table position and UpdateTableLayout methodBug

Public API and Backward Incompatible Changes

This section lists public API changes that were introduced in Aspose.Words 20.2. It includes not only new and obsoleted public methods, but also a description of any changes in the behavior behind the scenes in Aspose.Words which may affect existing code. Any behavior introduced that could be seen as regression and modifies the existing behavior is especially important and is documented here.

FieldMergingArgsBase.FieldValue made settable

Related issue: WORDSNET-19750

The customer was using the FieldMergingArgs.Text property and wanted the provided value to be formatted according to the format specified in the field being merged. We have made the FieldMergingArgsBase.FieldValue property settable so that instead of setting Text the user can set FieldValue which takes formatting into account instead of simply replacing the field.

/// <summary>
/// Gets or sets the value of the field from the data source.
/// </summary>
/// <remarks>
/// This property contains a value that has just been selected from your data source
/// for this field by the mail merge engine. You can also replace the value by setting the property.
/// </remarks>
public object FieldValue
    get { return mFieldValue; }
    set { mFieldValue = value; }

Word 2019 version set by default

Ref: WORDSNET-19908

Due to the fact that submissions to the support service regarding different default spacing values for the paragraph have become more frequent, it was decided to change the default version of MS Word. Now, this version is MSWordVersion.Word2019. In most cases, the issue appeared when the customers created documents in WPS Office that do not write default spacing values for the paragraph in a document to be saved. When opening such documents in Aspose.Words, the values actual for MSWord 2007 were substituted because it was the default version before this release.

Now the code:

Document doc = new Document("document.docx");

will be identical to:

LoadOptions lo = new LoadOptions();
lo.MswVersion = MsWordVersion.Word2019;
Document doc = new Document("document.docx", lo);

To achieve the previous behavior, it is necessary to explicitly specify the version:

LoadOptions lo = new LoadOptions();
lo.MswVersion = MsWordVersion.Word2007;
Document doc = new Document("document.docx", lo);