Simpler way to implement a Windows SCM service.

[Korporal]

I understand that the Windows Service model and SCM, are platform specific but is there really no easier way to code a service now, other than this rather involved and convoluted "recipe"?

Who has the time to "rewrite" this and that class and all the other steps. I've built Windows services many times in both C and C# (.Net F) and think we need a simpler approach for doing so under .Net.

There isn't even a template for such a project, so I'm asking what would it take to create a .Net version of the older ServiceBase and other classes? Having an identical set of classes to what was used in .Net F would be so helpful.

[tacosontitan]

As someone who actively works with Windows services in both .NET Framework and modern .NET, I completely disagree with the idea of having an identical set of classes for that. I prefer the modern worker service approach much more than the classic ServiceBase approach.

There is a template for worker services and this template can easily be extended to add support for a Windows service, and there isn't a ton of rewriting needed to facilitate it.

https://learn.microsoft.com/en-us/dotnet/core/extensions/windows-service

[Korporal]

Hi, @tacosontitan I'd like to simply rebuild an existing service app, with a plug-in compatible set of service classes with the same interfaces as we had in .Net F. I would prefer to avoid changing the design at all. I'm sure you are right and that the more "modern" design is fine, but I'm seeking to port a complex service and - like any sensible developer - I'm trying to do as little as possible!

In that article, where are the various optional events that a service can handle? like shutdown, start, pause, continue, power fail and so on?

I wonder if a nuget package could be written that mimics the older .Net F service classes...

[Korporal]

Hmm, seems there is a .Net 8 version of all this, how did I miss this?

[Korporal]

Yup, seems exactly what I was seeking, amazing!