Page 2 of 2
Re: Targeting Web Application to net10.0-windows and new (2026.2) merged packages
Posted: Thu Jul 23, 2026 9:56 pm
by Lech Kulikowski
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.
Re: Targeting Web Application to net10.0-windows and new (2026.2) merged packages
Posted: Fri Jul 24, 2026 4:45 pm
by ssh
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
Re: Targeting Web Application to net10.0-windows and new (2026.2) merged packages
Posted: Mon Jul 27, 2026 9:10 pm
by Lech Kulikowski
Hello,
We will check it and will let you know the result.
Thank you.
Re: Targeting Web Application to net10.0-windows and new (2026.2) merged packages
Posted: Tue Jul 28, 2026 7:31 am
by Lech Kulikowski
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.