.NetCore Versions deprecated, but main versions require -windows .NET version

Stimulsoft Reports.NET discussion
Post Reply
appdev-occunet
Posts: 3
Joined: Mon Apr 27, 2026 4:19 pm

.NetCore Versions deprecated, but main versions require -windows .NET version

Post by appdev-occunet »

We have a .NET 8.0 API where our reports are rendered. It has been referencing Stimulsoft.Reports.Engine.NetCore. It runs as an App Service in Azure. An Azure App Service does not allow access to Microsoft.Net.Sdk.Desktop (net8.0-windows), it only allows Microsoft.Net.Sdk (net8.0). We have a base assembly that contains our reporting engine wrapper where the data sources are populated, templates are retrieved, and the report is rendered. The rendered report is then retrieved through an API call. Our frontend is a WPF app which references Stimulsoft.Reports.Wpf. We have issues with rendering in the WPF because the WPF references the shared library that references Stimulsoft.Reports.Engine.NetCore, and the Stimulsoft.Base assembly is different between the two Nuget packages.

When researching a fix, I saw that the .NetCore versions are deprecated, but the regular versions (Stimulsoft.Reports.Engine) require a -windows version because they reference pieces of System.Windows.Forms. I cannot deploy that to an App Service in Azure. Do you have it in your roadmap to remove the dependency on Windows Forms for the engine? The .NetCore version didn't have it. We need the base libraries of Stimulsoft not to have a Windows dependency so they can be deployed to Azure.

Is there a workaround in the meantime?
  • Company.Shared.Reporting - engine wrapper - queries data and renders reports - references Stimulsoft.Reports.Engine (previously .NetCore version)
  • Company.Api - .NET MVC API that renders the reports - references Company.Shared.Reporting
  • Company.Wpf - WPF project that is the app frontend - references Company.Shared.Reporting and Stimulsoft.Reports.Wpf
Max Shamanov
Posts: 1135
Joined: Tue Sep 07, 2021 10:11 am

Re: .NetCore Versions deprecated, but main versions require -windows .NET version

Post by Max Shamanov »

Hello.

Could you please clarify what version you are using?

Thank you.
appdev-occunet
Posts: 3
Joined: Mon Apr 27, 2026 4:19 pm

Re: .NetCore Versions deprecated, but main versions require -windows .NET version

Post by appdev-occunet »

We are on 2026.2.1.
Lech Kulikowski
Posts: 7768
Joined: Tue Mar 20, 2018 5:34 am

Re: .NetCore Versions deprecated, but main versions require -windows .NET version

Post by Lech Kulikowski »

Hello,

We apologize for the delay, but we need some extra time to investigate the issue thoroughly. We will let you know about the result as soon as possible.

Thank you for your patience.
#20185
Lech Kulikowski
Posts: 7768
Joined: Tue Mar 20, 2018 5:34 am

Re: .NetCore Versions deprecated, but main versions require -windows .NET version

Post by Lech Kulikowski »

Hello,

The regular version (without .NET Core), starting from release 2026.2.1, now includes net8.0-windows and net8.0 assemblies. NuGet will automatically install the one that matches the TargetFramework of your project. The assemblies for net8.0 in this package are exactly the same as in .NET Core.

Thank you.
appdev-occunet
Posts: 3
Joined: Mon Apr 27, 2026 4:19 pm

Re: .NetCore Versions deprecated, but main versions require -windows .NET version

Post by appdev-occunet »

Lech Kulikowski wrote: Wed May 06, 2026 7:02 am Hello,

The regular version (without .NET Core), starting from release 2026.2.1, now includes net8.0-windows and net8.0 assemblies. NuGet will automatically install the one that matches the TargetFramework of your project. The assemblies for net8.0 in this package are exactly the same as in .NET Core.

Thank you.
That's excellent news. I will give it a try and post back with the results. Thank you.
Lech Kulikowski
Posts: 7768
Joined: Tue Mar 20, 2018 5:34 am

Re: .NetCore Versions deprecated, but main versions require -windows .NET version

Post by Lech Kulikowski »

Hello,

Ok. Please let us know about the result.

Thank you.
Post Reply