Repository navigation
Roadmap #219
Copy link
Copy link
Open
Labels
Description
Taking over maintenance work for now, here's a rough roadmap I want to follow.
Join the discussion of you have any ideas / wishes.
Phase 1 ✅
- Remove references to defunct codeplex sites
- Update project files to SDK format
- Update to .NET Framework 4.6.2 (minimum supported netfx version)
- Drop Client Profiles support
- Drop Mono support
- Update build files or replace them with dotnet CLI commands
- Add GitHub Actions to ensure every change can be built
- Update dependencies, while keeping the compatibility as is in a first step
- Check that all referenced images still work
- Test all the features
- Release v1.5.1 as a new NuGet package of the modernized project setup
- Update repository website URL
Phase 2 ✅
- Tag old versions and create GitHub releases with release notes
- Clean up the issue tracker and close / merge open pull requests
- Release v1.5.2 & NuGet packages
- Consider taking over some improvements from forks
Phase 3 ✅
- Update everything to .NET Standard 2.0 / .NET 8: Target .NET Standard 2.0 / .NET 8 / .NET 10 #222
- HtmlRenderer.Core: netstandard2.0 / net8.0
- HtmlRenderer.PdfSharp: netstandard2.0 / net8.0
- HtmlRenderer.WinForms: net8.0-windows
- HtmlRenderer.WPF: net8.0-windows
- Deprecate Mono NuGet package
- Use the new MigraDoc & PDFsharp implementation: Update PDFsharp for Version 6.x #221
- Release v1.6 & NuGet packages
Phase 4
- Expand HTML support via HtmlKit: Use HtmlKit tokenizer for HTML5 parsing #243
- Expand CSS support via vendored ExCSS: Add a real, spec-compliant CSS3/4 engine (ported from ExCSS via PeachPDF) #244
- Close additional gaps (via PeachPDF)
- Release v2.0 & NuGet packages
Future
- Investigate performance improvements utilizing .NET 8 / 10 features
- Create a GitHub Pages site as stand-in for the CodePlex & CodePlex Archive site
- Consider support for WinUI
- Consider support for Avalonia UI: https://github.com/AvaloniaUI/Avalonia.HtmlRenderer
- Consider support for Uno Platform
- Consider support for a generic SkiaSharp renderer
Reactions are currently unavailable
Activity
eXpl0it3r commentedon Dec 10, 2025
@ArthurHub Pinging you here, since I don't know if you're monitoring that one Gmail account 😄
What I need your help with:
ArthurHub commentedon Dec 11, 2025
Definitely better on GitHub :)
added you to all NuGet packages and updated the URL
thanks for reviving this project!
mstancombe commentedon Mar 13, 2026
hey @eXpl0it3r I'd be happy to make a PR to pull in some of the stuff we've been doing out in fork land. We added some more skia features and have made a bunch of other small fixes as well, but having this finally come back to the mother branch would be great :)
eXpl0it3r commentedon Mar 13, 2026
@mstancombe That would be awesome! I've spent some time in fork land, but it's vast and lots of abandoned work. As such, it would be awesome if someone could condense some of the changes and PR them. ❤️
jhaygood86 commentedon Jul 14, 2026
I started creating PRs to bring this project up to parity with PeachPDF -- which has 10 years of HTML5 + CSS3/4 features implemented, and gets new features all the time. There are going to be some gaps since PeachPDF focuses entirely on print rendering, and it uses a private fork of PdfSharpCore which allows me to improve the PDF output directly where PdfSharp falls short, but for where I can, I'll gladly bring the improvements over.
The current roadmap will be: