We are announcing a significant update to the versions of the various frameworks utilized for compilation of our products. All changes outlined in this note will be incorporated into version 2024.2 of Stimulsoft Reports, Dashboards, and Forms.

.NET 5.0 and Blazor

Starting with the upcoming version of our products Stimulsoft Reports.BLAZOR and Stimulsoft Dashboards.BLAZOR, we will discontinue support for .NET 5.0. This version was deemed obsolete and ceased to receive support from Microsoft as of May 10, 2022. Beginning with version 2024.2, these products will be compatible with .NET 6.0 and newer versions.

.NET Standard 2.1

This specification was designed to be universally applicable for apps utilizing both the .NET Framework and .NET Core across diverse platforms. With the introduction of .NET 5.0, a unified API was adopted for similar purposes, making this specification obsolete. Beginning with version 2024.2, the minimum required version for all products utilizing the .NET Core Framework will be .NET Core 3.1. Despite being outdated, it is still used in previously created and operational projects.

.NET 8.0

Starting with version 2024.2, we are incorporating comprehensive support for the .NET 8.0 version across all our products built on the .NET framework. While our products have functioned properly in projects utilizing this version previously, we will now compile our libraries using the .NET 8.0 SDK and update all corresponding NuGet packages. This enhancement will enable you to leverage all the features offered by the modern .NET 8.0 framework.


In other words, beginning with the next version of our products built on the .NET framework, full support for compilation will be extended to the following frameworks:

  • .NET Framework 4.5.2
  • .NET Framework 4.7.2
  • .NET Core 3.1
  • .NET 6.0
  • .NET 8.0

For our products Stimulsoft Reports.AVALONIA, Stimulsoft Reports.BLAZOR and Stimulsoft Dashboards.BLAZOR, compilation for the following frameworks will be supported:

  • .NET 6.0
  • .NET 8.0

All other framework versions are also fully compatible with our products, and when utilizing libraries, their minimum required version will be loaded.

What does this mean in practice?

For instance, if your project utilizes the .NET Framework 4.6.x, then the version compiled for 4.5.2 will be used to execute our components. Similarly, if you are using the .NET Framework 4.8.x, the version compiled for 4.7.2 will be used to run our components. This principle also applies to the .NET 5.0 and .NET 7.0 frameworks, where the corresponding minimum required version will be utilized for the operation of our products.

All our components undergo thorough testing and are fully compatible with all specified framework versions, including their minor updates and newer versions.
By using this website, you agree to the use of cookies for analytics and personalized content. Cookies store useful information on your computer to help us improve efficiency and usability. For more information, please read the privacy policy and cookie policy.