Upgrade Guide for Embedded Reporting Applications in Bold Reports

How Does the Bold Reports Embedded Reporting Upgrade Work in the Latest Version? Can We Upgrade Packages Without Halting the Production Process?

Overview

Upgrading to the latest version of Bold Reports Embedded Reporting is designed to be straightforward and safe. The upgrade process preserves your existing reports, configurations, and application settings. However, in a live production environment, certain precautions are required to maintain system stability and prevent runtime issues.

This article explains the recommended upgrade procedure, why halting production is necessary, and how to safely roll back and resume operations.

Upgrade Procedure:

Follow the steps below to upgrade your application to the latest version of Bold Reports:

1. Halt the Production Process

   Stop the currently running application before applying any changes. This ensures a safe and controlled upgrade process.

2. Upgrade the NuGet Package

   Update the BoldReports NuGet package to the latest version (or a specific required version).

   

3. Update Script References

   If using CDN Scripts:

   Update the script references to the version you have upgraded to (in case of CDN usage).

   

   If using Offline Scripts:

   Update the script references to the new version (typically added via the BoldReports.JavaScript NuGet package).

   

   Ensure that all updated script references are correctly included in your .cshtml file.

   

Note:

In .NET Core applications, hot-swapping dependencies or live patching is not supported by the runtime. As a result:

• You cannot upgrade the application while it is actively running.
• Halting the production process is essential to:
  • Unload the current application instance
  • Apply the package upgrades
  • Restart the application with updated dependencies

This approach ensures:

• System stability
• Prevention of runtime conflicts
• A controlled environment for validating the upgrade

Rollback Strategy

Before proceeding the upgrade, it is strongly recommended to:

• Take a full backup of your application and configuration files.
• Document the current package versions and script references.
• Test the upgrade in a staging environment before applying it to production.

If any issues occur, you can roll back by:

• Reverting to the previous NuGet package version
• Restoring the original script references
• Redeploying the backup

Resume Production

After completing and validating the upgrade:

• Restart the application
• Resume the production process

While Bold Reports supports seamless upgrades, production environments require a controlled approach. Due to .NET Core limitations, halting the application during the upgrade is mandatory. With proper planning, backups, and rollback strategies, you can perform a smooth and reliable upgrade without impacting production stability.