Repository navigation
Target .NET Standard 2.0 / .NET 8 / .NET 10 #222
Description
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.
- HtmlRenderer.Core: netstandard2.0 / net8.0
- HtmlRenderer.PdfSharp: netstandard2.0 / net8.0
- HtmlRenderer.WinForms: net8.0-windows
- HtmlRenderer.WPF: net8.0-windows
- HtmlRenderer.Mono: Deprecated
Additional related updates
- Update PDFsharp: Update PDFsharp for Version 6.x #221
- Use System.Text.Json instead of custom/hacky IndexOf JSON parsing
Activity
eXpl0it3r commentedon Dec 22, 2025
Implemented with #234
LarsKloseLke commentedon Jul 20, 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?
eXpl0it3r commentedon Jul 20, 2026
That's correct, but I haven't gotten around to publishing new NuGet packages since the merge.
The goal is also to update to the latest PDFSharp version as to actually stay true to the .NET Standard 2.0 / .NET 8 promise.
See also the Roadmap #219 and PDFSharp update issue #221
LarsKloseLke commentedon Jul 29, 2026
@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?
eXpl0it3r commentedon Jul 29, 2026
@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?
LarsKloseLke commentedon Jul 29, 2026
@eXpl0it3r I'm sorry - I was referring to HtmlRenderer.Wpf
eXpl0it3r commentedon Jul 29, 2026
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 😄
eXpl0it3r commentedon Jul 29, 2026
@LarsKloseLke Hot from the press 😄
Hope this works, as I didn't test the actual compatibility, as such let me know!
LarsKloseLke commentedon Jul 29, 2026
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 👍