We’re happy to announce the release of GroupDocs.Viewer for .NET v26.8, available as of August 2026. This release introduces a major architectural improvement with TFM-split NuGet packaging, four new features — including support for hidden PDF annotations, configurable resolution for WordProcessing documents, and page numbering, — and addresses eight critical bugs affecting PDF, WordProcessing, EML, and EPSF rendering.
What’s new in this release
- [New feature] Implement TFM-Split NuGet Packaging for GroupDocs.Viewer (VIEWERNET-5719)
- [New feature] Implement exposing of annotations in PDF that are hidden by default during rendering (VIEWERNET-5607)
- [New feature] Add ability to specify horizontal and vertical resolution in WordProcessing options while rendering WordProcessing documents to raster formats (VIEWERNET-5700)
- [New feature] Add page numbering for WordProcessing documents during rendering (VIEWERNET-5702)
- [Bug] Special characters incorrectly rendered and table borders are missing while converting EML to HTML and raster formats (VIEWERNET-5620)
- [Bug] Issue with missing comments while rendering PDF (VIEWERNET-5654)
- [Bug] DOCX to HTML rendering is incorrect with Arabic characters and EnableOpenTypeFeatures option enabled (VIEWERNET-5681)
- [Bug] EPSF format support is limited. An error occurred while parsing the EPSF file content (VIEWERNET-5683)
- [Bug] Mismatch between actual dimensions of rasterized archives and calculated by GetViewInfo (VIEWERNET-5737)
- [Bug] [UI] Groupdocs viewer 8.0.7/8.1.x - Pages not loaded in viewer are not available in print preview (VIEWERNET-5615)
Public API changes
Added
Options.WordProcessingOptions.HorizontalResolutionproperty ofInt32type (VIEWERNET-5700)Options.WordProcessingOptions.VerticalResolutionproperty ofInt32type (VIEWERNET-5700)WordsPageNumberLocationenum (VIEWERNET-5702)Options.WordProcessingOptions.PageNumberLocationproperty ofWordsPageNumberLocationtype (VIEWERNET-5702)
Modified
RenderNotesproperty ofBooleantype: its “area” was expanded to cover the PDF documents too. (VIEWERNET-5607)
Removed
None
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.
How to get the update
NuGet
Upgrade to the latest GroupDocs.Viewer package via NuGet. The TFM-split packaging automatically installs the correct platform-specific sub-package:
Direct download
Download assemblies from the GroupDocs.Viewer for .NET download page