Exago v2026.3 Release Notes

Exago Support Updates

• Support for Exago releases has changed as of the release of v2024.4.1. Going forward, only the most current major release and previous two major releases are supported. Upgrade to the most current release for the most up to date support.
• Release notes may appear identical across supported major versions because it includes fixes applied to multiple affected releases.
• Exago has upgraded from .NET Framework 4.5 to .NET Framework 4.8, and includes all necessary library support.
• Exago has upgraded to .NET 10 from .NET Framework for v2026.3 and later.
• If you are planning to upgrade or are waiting for bug fixes, prioritize testing in your test environment before promoting into your production environment.

v2026.3.1 Release Notes

We are proud to release Exago BI v2026.3.1!  

2026-08-10

Supported Versions & Release History

These release notes apply to all supported major versions simultaneously. When a patch is released, it ships across every supported track at the same time; identical content across versions is expected.

Note: The version listed as "Current" will be superseded by the next dated release.

If you're on v2026.2.1: You're up to date until the next dated release. This release covers all changes since v2025.3.2, including everything from the interim v2026.1.1 patch.

How version numbers work: v[year].[release].[patch] — the patch digit increments for hotfixes within a release slot.

Overview

This release migrates the Exago Reporting Platform from the legacy .NET Framework System.Web hosting model to a platform targeting .NET 10. It replaces or modernizes the export, rendering, formula, data-access, and messaging stacks, restructures configuration and session handling, and closes a significant backlog of security findings identified against the legacy 4.8 codebase.

For full step-by-step migration procedures, configuration file contents, and troubleshooting detail, refer to the companion Customer Migration Guide, Distributed Session Backend Configuration.

Who Should Read This

Users who are migrating their environment from an existing Exago deployment, or relying on the classic.  StateServer session model, legacy WebServiceAPI, CData-managed drivers, or export/scheduler workflows built on .NET Framework–era libraries.

Release Highlights

• Chart/widget rasterization moved from wkhtmltoimage to headless Chromium via Puppeteer.

Platform & Software Requirements

All migrated projects target net10.0 (rollForward: latestPatch). 

Breaking Changes & Compatibility Gaps

• Redis is the only supported state server. MySQL is not supported for session management.

Configuration & File Locations

• web.config / app.config are retired. All UI, API, and Scheduler configuration now lives in appsettings.json files (plus environment overlays). Configurations must be added manually.
• Static files and configuration (WebReports.xml, themes, images, CSS) now live under wwwroot (e.g. wwwroot/Config/WebReports.xml, wwwroot/ApplicationThemes). Copy required static files into the new locations and test them before go-live.

Scheduler

• Always deploy the new Scheduler build to a fresh, separate folder. Installing directly over an existing Scheduler install can corrupt the running installation.
• Any custom Scheduler .dll code must be recompiled to target .NET 10; legacy .NET Framework 4.8 assemblies will not load.

Known Issues

• Emoji rendering is not supported.
• CrossTab visualizations PDF exports have issues when the column widths are larger than actual page widths.
• ExpressView PDF export on large reports have page-break spacing issues due to excessive whitespace in edge cases.

Migration Guidelines

• Deploy this release of Exago as new installation. Do not overwrite an existing installation setup.
• If a custom application/assembly is shared between the website and the Web API, confirm each app gets its own copy of required files in its own directory.

For more information, see Distributed Session Backend Configuration.