Latest release (August 2026)

This significant GroupDocs.Viewer for .NET 26.8 release contains a lot of new features, several bug fixes, and the most important — the new type of NuGet package configuration called the TFM-split packaging. Public API was expanded with new members, and some existing members were modified to represent the new features.

Full list of changes in this release

KeyCategorySummary
VIEWERNET‑5719New featureImplement TFM-Split NuGet Packaging for GroupDocs.Viewer
VIEWERNET‑5607New featureImplement exposing of annotations in PDF that are hidden by default during rendering
VIEWERNET‑5700New featureAdd ability to specify horizontal and vertical resolution in WordProcessing options while rendering WordProcessing documents to raster formats
VIEWERNET‑5702New featureAdd page numbering for WordProcessing documents during rendering
VIEWERNET‑5620BugSpecial characters incorrectly rendered and table borders are missing while converting EML to HTML and raster formats
VIEWERNET‑5654BugIssue with missing comments while rendering PDF
VIEWERNET‑5681BugDOCX to HTML rendering is incorrect with Arabic characters and EnableOpenTypeFeatures option enabled
VIEWERNET‑5683BugEPSF format support is limited. An error occurred while parsing the EPSF file content
VIEWERNET‑5737BugMismatch between actual dimensions of rasterized archives and calculated by GetViewInfo
VIEWERNET‑5615Bug[UI] Groupdocs viewer 8.0.7/8.1.x - Pages not loaded in viewer are not available in print preview

New features

VIEWERNET‑5719

The GroupDocs.Viewer NuGet package was totally redesigned. Now there is no separate GroupDocs.Viewer.CrossPlatform package anymore. The main idea of the TFM-split packaging is that now the GroupDocs.Viewer NuGet package serves as a lightweight router package, which internally does not contain the binaries (DLL files). Instead it contains the NuSpec with all metadata like ID, versioning and so on, but when binary files it contains the empty placeholder files like “_._”, that is a NuGet convention meaning “this TFM is supported, but no assemblies ship from this package.”. When installing by the user, the NuGet package manager reads the actual platform (framework) of a user’s project and installs the one of the necessary sub-packages: “GroupDocs.Viewer.Net462”, “GroupDocs.Viewer.Net60”, or “GroupDocs.Viewer.Net60.Windows”. So, if your project is built for .NET Framework 4.6.2 or above, and you update the GroupDocs.Viewer 26.4 to the latest 26.8 through the NuGet package manager, there will be installed “GroupDocs.Viewer.26.8.0” and dependent “GroupDocs.Viewer.Net462.26.8.0” packages.

VIEWERNET‑5607

Now it is possible to enable rendering of hidden by default popup annotations (baloon hints) in PDF files by using already existing RenderNotes property — its meaning was changed for the PDF documents. This article section describes this feature in details.

VIEWERNET‑5700

Like for the Spreadsheet documents in previous release, the version 26.8 allows to specify a horizontal and vertical resolution in DPI unit when rendering the input WordProcessing documents to the raster formats (PNG and JPEG). This is done with the new public properties HorizontalResolution and VerticalResolution in WordProcessingOptions class. Both the properties have a default value of 96 DPI. It can be manually set within the range [72..600] DPI. This feature is described in detail in corresponding section of the article about rendering WordProcesing documents.

VIEWERNET‑5702

Starting with this version with a new property PageNumberLocation, that was added to the WordProcessingOptions class, it is possible to forcibly add the page number to the WordProcessing document during its rendering and even to specify a location of the page number on the page. This new feature is described here.

Public API changes

Added

Modified

  • RenderNotes property of Boolean type: its “area” was expanded to cover the PDF documents too. (VIEWERNET‑5607)

** Removed**

None