GroupDocs.Assembly for .NET 26.6 – June 2026 Release Highlights ^[draft]

GroupDocs.Assembly for .NET 26.6 is now available. This release introduces a modular NuGet package layout, updates the underlying document‑generation engines, resolves a security advisory, and fixes a JSON date‑parsing issue.

What’s new in this release

Public API changes

GroupDocs.Assembly for .NET 26.6 introduces no public API changes and no behaviour changes in the document‑assembly engine itself.

New features

NuGet package split — per-target-framework runtime packages

To keep the package well under NuGet’s 250 MB limit as more target frameworks are added, GroupDocs.Assembly is now published as a lightweight router metapackage plus one runtime package per target framework:

• GroupDocs.Assembly — the router (a few KB). You still install this; nothing changes for consumers.
• GroupDocs.Assembly.Net40Client — .NET Framework 4.0 Client Profile assemblies
• GroupDocs.Assembly.Net462 — .NET Framework 4.6.2 assemblies
• GroupDocs.Assembly.NetStandard20 — .NET Standard 2.0 assemblies (Mono, Unity, Xamarin, .NET Core 3.x)
• GroupDocs.Assembly.Net60 — .NET 6 assemblies
• GroupDocs.Assembly.Net80 — .NET 8 assemblies
• GroupDocs.Assembly.Net100 — .NET 10 assemblies

When you install GroupDocs.Assembly, NuGet automatically resolves the runtime package matching your project’s target framework. Install command, namespaces, types and public API are unchanged — you’ll just see one extra package (the runtime package for your TFM) under Dependencies.

Deprecation notice — Net40Client and NetStandard20 will be removed in ~3 months (planned: September 2026). Customers still installing GroupDocs.Assembly.Net40Client or GroupDocs.Assembly.NetStandard20 should migrate to a supported runtime package — GroupDocs.Assembly.Net462 for .NET Framework, or GroupDocs.Assembly.Net60 (or later: Net80, Net100) for .NET