Targeting Web Application to net10.0-windows and new (2026.2) merged packages
Targeting Web Application to net10.0-windows and new (2026.2) merged packages
Hello,
what is the right way to target a web application to net10.0-windows?
TF net10.0-windows resloves Stimulsoft.Reports.Web to net10.0 and Stimulsoft.Reports.Engine to net10.0-windows7.0. There are issues with dependencies, i.e. Stimulsoft.Drawing.
TF net10.0 resolves Stimulsoft assemblies to net10.0 with no issues, but there are issues with third party windows-only-packages (net10.0-windows).
With NetCore naming it was easy to reference the right dependency graph by the package name.
Regards,
SSH
what is the right way to target a web application to net10.0-windows?
TF net10.0-windows resloves Stimulsoft.Reports.Web to net10.0 and Stimulsoft.Reports.Engine to net10.0-windows7.0. There are issues with dependencies, i.e. Stimulsoft.Drawing.
TF net10.0 resolves Stimulsoft assemblies to net10.0 with no issues, but there are issues with third party windows-only-packages (net10.0-windows).
With NetCore naming it was easy to reference the right dependency graph by the package name.
Regards,
SSH
-
Lech Kulikowski
- Posts: 7822
- Joined: Tue Mar 20, 2018 5:34 am
Re: Targeting Web Application to net10.0-windows and new (2026.2) merged packages
Hello,
The regular version (without .NET Core), starting from release 2026.2.1, now includes net-windows and net assemblies. NuGet will automatically install the one that matches the TargetFramework of your project. The assemblies for net in this package are exactly the same as in .NET Core.
Thank you.
The regular version (without .NET Core), starting from release 2026.2.1, now includes net-windows and net assemblies. NuGet will automatically install the one that matches the TargetFramework of your project. The assemblies for net in this package are exactly the same as in .NET Core.
Thank you.
Re: Targeting Web Application to net10.0-windows and new (2026.2) merged packages
the problem is the assemblies net10.0 (Web) and net10.0-windows (Engine) are not compatible. there is no Stimulsoft.Drawing assembly in the Stimulsoft.Reports.Engine (net10.0-windows7.0). so the viewer cannot render the report.
{"Could not load file or assembly 'Stimulsoft.Drawing, Version=2026.2.3.0, Culture=neutral, PublicKeyToken=73df5cf8c5255bdd'. The system cannot find the file specified.":"Stimulsoft.Drawing, Version=2026.2.3.0, Culture=neutral, PublicKeyToken=73df5cf8c5255bdd"}
at Stimulsoft.Report.Web.StiFontsHelper.GetCustomOpenTypeFontItems(Boolean allowLoadingCustomFonts)
at Stimulsoft.Report.Web.StiFontsHelper.GetCustomOpenTypeFontItems(Boolean allowLoadingCustomFonts)
at Stimulsoft.Report.Mvc.StiNetCoreViewer.RenderJsonParameters()
at Stimulsoft.Report.Mvc.StiNetCoreViewer.CreateChildControls()
at Stimulsoft.Report.Mvc.StiNetCoreViewer.Render(HtmlTextWriter writer)
at Stimulsoft.System.Web.UI.Control.RenderControl(HtmlTextWriter writer)
at Stimulsoft.Report.Mvc.StiNetCoreHelper.StiNetCoreViewer(IHtmlHelper htmlHelper, String ID, StiNetCoreViewerOptions options, Hashtable formKeys)
at Stimulsoft.Report.Mvc.StiNetCoreHelper.StiNetCoreViewer(IHtmlHelper htmlHelper, StiNetCoreViewerOptions options)
{"Could not load file or assembly 'Stimulsoft.Drawing, Version=2026.2.3.0, Culture=neutral, PublicKeyToken=73df5cf8c5255bdd'. The system cannot find the file specified.":"Stimulsoft.Drawing, Version=2026.2.3.0, Culture=neutral, PublicKeyToken=73df5cf8c5255bdd"}
at Stimulsoft.Report.Web.StiFontsHelper.GetCustomOpenTypeFontItems(Boolean allowLoadingCustomFonts)
at Stimulsoft.Report.Web.StiFontsHelper.GetCustomOpenTypeFontItems(Boolean allowLoadingCustomFonts)
at Stimulsoft.Report.Mvc.StiNetCoreViewer.RenderJsonParameters()
at Stimulsoft.Report.Mvc.StiNetCoreViewer.CreateChildControls()
at Stimulsoft.Report.Mvc.StiNetCoreViewer.Render(HtmlTextWriter writer)
at Stimulsoft.System.Web.UI.Control.RenderControl(HtmlTextWriter writer)
at Stimulsoft.Report.Mvc.StiNetCoreHelper.StiNetCoreViewer(IHtmlHelper htmlHelper, String ID, StiNetCoreViewerOptions options, Hashtable formKeys)
at Stimulsoft.Report.Mvc.StiNetCoreHelper.StiNetCoreViewer(IHtmlHelper htmlHelper, StiNetCoreViewerOptions options)
Re: Targeting Web Application to net10.0-windows and new (2026.2) merged packages
Web Application, TF net10.0-windows
2026.1:
Stimulsoft.Reports.Web.NetCore (net10.0)->Stimulsoft.Reports.Engine.NetCore (net10.0)
2026.2:
Stimulsoft.Reports.Web (net10.0)->Stimulsoft.Reports.Engine (net10.0-windows)
...so, it's not the same
2026.1:
Stimulsoft.Reports.Web.NetCore (net10.0)->Stimulsoft.Reports.Engine.NetCore (net10.0)
2026.2:
Stimulsoft.Reports.Web (net10.0)->Stimulsoft.Reports.Engine (net10.0-windows)
...so, it's not the same
-
Lech Kulikowski
- Posts: 7822
- Joined: Tue Mar 20, 2018 5:34 am
Re: Targeting Web Application to net10.0-windows and new (2026.2) merged packages
Hello,
Yes, there is an issue. At the moment, please use only the net10.0 target framework without the Windows-specific suffix.
We will review the packages and most likely Reports.Web will also be compiled for the -windows target framework.
Thank you.
#20439
Yes, there is an issue. At the moment, please use only the net10.0 target framework without the Windows-specific suffix.
We will review the packages and most likely Reports.Web will also be compiled for the -windows target framework.
Thank you.
#20439
-
Lech Kulikowski
- Posts: 7822
- Joined: Tue Mar 20, 2018 5:34 am
Re: Targeting Web Application to net10.0-windows and new (2026.2) merged packages
Hello,
The issue is fixed. It will be available with the release 2026.3.1
Thank you.
The issue is fixed. It will be available with the release 2026.3.1
Thank you.
Re: Targeting Web Application to net10.0-windows and new (2026.2) merged packages
Hello,
seems to be fixed, thanks.
the version number of the "Stimulsoft.System.dll" and "Stimulsoft.System.Web.dll" is still on 2026.2.4 (stimulsoft.reports.engine and stimulsoft.reports.web packages, just windows targets). could you please check this?
thank you.
SSH
seems to be fixed, thanks.
the version number of the "Stimulsoft.System.dll" and "Stimulsoft.System.Web.dll" is still on 2026.2.4 (stimulsoft.reports.engine and stimulsoft.reports.web packages, just windows targets). could you please check this?
thank you.
SSH
Re: Targeting Web Application to net10.0-windows and new (2026.2) merged packages
Hello,
there is a new issue with 2026.3.1.
var report = new Stimulsoft.Report.StiReport();
report.Render();
...throws exception
Could not load file or assembly 'System.Windows.Forms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. The system cannot find the file specified.
Web Application, TF net10.0-windows
SSH
there is a new issue with 2026.3.1.
var report = new Stimulsoft.Report.StiReport();
report.Render();
...throws exception
Could not load file or assembly 'System.Windows.Forms, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. The system cannot find the file specified.
Web Application, TF net10.0-windows
SSH
-
Lech Kulikowski
- Posts: 7822
- Joined: Tue Mar 20, 2018 5:34 am
Re: Targeting Web Application to net10.0-windows and new (2026.2) merged packages
Hello,
In this case, Reports.Web is compiled entirely for Windows and uses native GDI+ graphics, which is more stable and faster on the Windows platform.
You need to add one line to your project:
<UseWindowsForms>true</UseWindowsForms>
Thank you.
In this case, Reports.Web is compiled entirely for Windows and uses native GDI+ graphics, which is more stable and faster on the Windows platform.
You need to add one line to your project:
<UseWindowsForms>true</UseWindowsForms>
Thank you.
Re: Targeting Web Application to net10.0-windows and new (2026.2) merged packages
Hello,
you mean the end customer have to install the Desktop Runtime with a Web Application? it's a little bit confusing...
UseWindowsForms could be a workaround, but not the issue fix.
The merge of the NetCore packages in this form is a degradation for us, not an improvement
SSH
you mean the end customer have to install the Desktop Runtime with a Web Application? it's a little bit confusing...
UseWindowsForms could be a workaround, but not the issue fix.
The merge of the NetCore packages in this form is a degradation for us, not an improvement
SSH