winsw VS QuestPDF

And then set that up as a windows service with WinSw

I am using Windows Service Wrapper to convert some net programs (tor, frp, etc.) into autostart background services. It seems I can choose which user to use when launch these custom services. Coming from a Linux background, I am a little bit confused and overwhelmed by the Windows account and permission systems. I am wondering what's the best practice? Use Local System (probably not, it has very high privileges)? Local Service? Network Service? Or create separate local user account for each service? Ideally I would like to give them minimal permissions (just open and listen a few local ports, connect to the internet, read/write certain local files) and auto start them before logon. Thanks for your advice!

We use a third party library (winsw) to package our exe as a windows-serice

It's been a while since I don't do anything similar, but one of the most popular is NSSM (the Non-Sucking Service Manager) and another open and free alternative would be WinSW (Windows Service Wrapper).

And you look into winsw.

winsw

There are projects which wrap an existing exe file and handle the service stuff for you, for example winsw or DaemonMaster. Another option is to write the service yourself, there's a Go package for that: https://pkg.go.dev/golang.org/x/sys/windows/svc

No idea about RunAsService, but I too have a Dart executable running as a service and I am using WinSW and it runs without issue.

If the program can't run directly as a service itself, you need a wrapper. Back in the day a program called NSSM was popular for this, but it's been unmaintained for many years so now you should use WinSW which is MIT-licensed, modern, actively maintained and easy to use

QuestPDF looks really good (I haven't used it) but I believe they changed their license recently.

I used that same library it worked great the only issue I had was the users would often have to manually set the scaling to fit to a page. I'm sure I could've fixed this in other ways if I was more competent with CSS but ended up just switching to use https://github.com/QuestPDF/QuestPDF in a backend instead of doing everything in front end.

Give this a try: QuestPDF

I think you should ask these questions in related discussion on Github: https://github.com/QuestPDF/QuestPDF/discussions/491

May I introduce you to QuestPDF!

➡️ James Newton-King ♔ on Twitter: "Coming in .NET 8: Route tooling for ASP.NET Core" / Twitter ➡️ Announcing .NET Community Toolkit 8.1 ➡️ Uno Platform 4.7 – New Project Template, Performance Improvements and more ➡️ C# Advent 2022 Awards | Cross Cutting Concerns ➡️ GitHub - QuestPDF ➡️ DNF Summit 2023 ➡️ .NET Frontend Day

Like many have suggested, I also cast my vote on QuestPDF. No more +50MB library including a Chrome browser to render HTML so a PDF of it can be created, which took 2-3 seconds each time. But with QuestPDF, it's so much faster!

Also, the library is open-source, so you can take a look at the exact implementation of the layout engine. It is inspired by Flutter and WPF, though optimized for pageable content: https://github.com/QuestPDF/QuestPDF/tree/main/Source/QuestPDF/Elements