RulesEngine VS winsw

Check out the Microsoft Rules Engine. Source: am contributor and wrote a Blazor editor for it

Might be worth checking out the Microsoft Rules Engine. It's part of the Microsoft Open Source libraries, which I think come from their employees.

I am using Microsoft's library to create rules. If anyone has used this library could you give a hint if it is possible to write a rule with different output based on an input?

Looking around I found this https://github.com/microsoft/RulesEngine and it looks like it could be the magic bullet. I see input (Event), a workflow defined in JSON (user defined rules), and a result that indicates the success/failure. From there we have what we need to determine the appropriate action(s) that can be dynamically defined.

Searching around I found the concept of Business Rules Engines. Specifically, this dotnet iteration - https://github.com/microsoft/RulesEngine. Thought it doesn't solve all my issues, the concept does look like it will solve some of the more problematic customer specific rules like commissions and pricing. Does anyone have experience and/or provide their two cents?

From the documentation for Microsoft RulesEngine, it seems like RulesEngine is focused on generating UI/form validation logic. Is that right? Does it also support using rules against a LINQ provider and pushing Rules down into the underlying query (i.e. generating SQL where clauses based on rules)?

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