Target .NET Standard 2.0 / .NET 8 / .NET 10 #222
Description
Activity
- pinned this issue
on Dec 9, 2025 - linked a pull request that will close this issueSupport for .NET 6.0 & SkiaSharp Renderer #200
on Dec 10, 2025 - linked a pull request that will close this issueAdded basic .net 5 support #188
on Dec 10, 2025 - linked a pull request that will close this issueUpdate projects to .NET 8 or .NET Standard 2.0 #234
on Dec 22, 2025 - unpinned this issue
on Jul 19, 2026 I expected that after the merge of #234 the nuget packages would also only list net8.0/netstandard2.0 as dependency but they still require netfx 4.6.2 - am I missing something?
Reacted by tecAmoRaller@eXpl0it3r I noticed the 1.6.0 release (congrats!), but was stumped a bit at the same time: do you intentionally target .NET 8 only? I was hoping for a multi-targeting package that also still continues to support .NET 4.x as I am stuck to support that. Would this be feasible given the changes that were necessary for .NET 8? Or would you rather recommend to stay on 1.5.2 for .NET Framework, thus referencing different package versions per target?
@LarsKloseLke We're multi-targeting .NET 8 and .NET Standard 2.0 which is compatible with .NET Framework 4.x. As such you should have no trouble to use the new NuGet package in both a .NET 8/9/10 and .NET Framework project.
Or are you referring to the WinForms / WPF variants?
@eXpl0it3r I'm sorry - I was referring to HtmlRenderer.Wpf
Ah, I didn't really think about this before. We can't target WPF and WinForms for netstandard2.0, but we can just multi-target for .NET 8 and .NET Framework 4.6.2. I'll prepare a release for 1.6.1 which includes this.
Regardless, I still highly recommend to update to .NET 8 any beyond 😄
@LarsKloseLke Hot from the press 😄
Hope this works, as I didn't test the actual compatibility, as such let me know!
Thanks for the quick response - very much appreciated! Just tried it out and the WPF HtmlPanel from 1.6.1 works just fine as expected under net48 👍
Reacted by Lukas Dürrenberger
Newer .NET versions provide a lot of performance and general language improvements.
We should be able to retain .NET Framework compatibility by continuing to support .NET Standard 2.0 for the Core library.
For WPF and WinForms the compatibility needs to be broken in order to support the newer .NET versions (afaik).
But to benefit from all the improvements one should multi-target those libraries that support the .NET Standard 2.0.
Additional related updates