3 ms·
That's a very different can of worms. I've used third party libraries for Windows Services since forever because the .NET Framework templates were never great a
by WorldMaker 4y ago
That's a very different can of worms. I've used third party libraries for Windows Services since forever because the .NET Framework templates were never great and Windows Services are a bad idea that are dumb to create and I think awful to maintain/manage.
At this point, personally, given the choice, I'd rather just create boring CLI applications that I can stick in cron jobs (or Windows Scheduled Tasks) than ever create another Windows Service if I can avoid it.
Given how dumb it is to create Windows Services and how dumb it is getting to create systemd-style services for Linux I can't possibly imagine how anyone could abstract that well cross-platform. That sounds like an awful minefield to create lowest common denominators that no one likes.
I think we already have such a cross-platform abstraction: it's classic CLI apps and whatever task runners you can find/stomach. .NET Core/.NET 5+ is great at cross-platform CLI apps.
- ocdtrekkie 4y agoLowest common denominators work great though, arguably nearly every classic Visual Studio template is a lowest common denominator. Here's one WinForm the starts when you press run. And there's a dozen ways that the way that comes out of the box needs to be changed, but it works out of the box. I think the .NET Core templates are really demonstrating a lack of understanding of why Visual Studio has thrived for this long.