Hello,
We have test examples for net10.0 and net10.0-windows, and everything is tested and works correctly. The first does not require System.Windows.*; the second does.
Please send your project for analysis.
Thank you.
Targeting Web Application to net10.0-windows and new (2026.2) merged packages
-
Lech Kulikowski
- Posts: 7826
- Joined: Tue Mar 20, 2018 5:34 am
Re: Targeting Web Application to net10.0-windows and new (2026.2) merged packages
Hello,
you are right, it works. the issue is the new dependency to winforms and desktop runtime.
web application, net10.0-windows
Stimulsoft 2026.1, NetCore packages: no WinForms dependency and therefore no Desktop Runtime is required.
Stimulsoft 2026.3, merged packages: WinForms dependency and therefore Desktop Runtime is required.
there are three project states: net10.0, net10.0-windows, net10.0-windows with WinForms/WPF. Not every "-windows" project need a WinForms/WPF support.
NetCore package line was a really great choice for us. we will now attempt to switch to the net10.0 target.
Thank you.
SSH
you are right, it works. the issue is the new dependency to winforms and desktop runtime.
web application, net10.0-windows
Stimulsoft 2026.1, NetCore packages: no WinForms dependency and therefore no Desktop Runtime is required.
Stimulsoft 2026.3, merged packages: WinForms dependency and therefore Desktop Runtime is required.
there are three project states: net10.0, net10.0-windows, net10.0-windows with WinForms/WPF. Not every "-windows" project need a WinForms/WPF support.
NetCore package line was a really great choice for us. we will now attempt to switch to the net10.0 target.
Thank you.
SSH
-
Lech Kulikowski
- Posts: 7826
- Joined: Tue Mar 20, 2018 5:34 am
Re: Targeting Web Application to net10.0-windows and new (2026.2) merged packages
Hello,
We will check it and will let you know the result.
Thank you.
We will check it and will let you know the result.
Thank you.
-
Lech Kulikowski
- Posts: 7826
- Joined: Tue Mar 20, 2018 5:34 am
Re: Targeting Web Application to net10.0-windows and new (2026.2) merged packages
Hello,
You are correct. Previously, a net10.0-windows project could use the compatible net10.0 assemblies without a WinForms dependency.
With the merged Windows package, native Windows GDI graphics are now used, providing better performance and improved stability. The downside is that the project must enable <UseWindowsForms>true</UseWindowsForms> and requires the .NET Desktop Runtime.
If you do not need the -windows target for a specific reason, there is generally no benefit in using it, so targeting net10.0 is preferable.
Thank you.
You are correct. Previously, a net10.0-windows project could use the compatible net10.0 assemblies without a WinForms dependency.
With the merged Windows package, native Windows GDI graphics are now used, providing better performance and improved stability. The downside is that the project must enable <UseWindowsForms>true</UseWindowsForms> and requires the .NET Desktop Runtime.
If you do not need the -windows target for a specific reason, there is generally no benefit in using it, so targeting net10.0 is preferable.
Thank you.