Remote.Linq VS RulesEngine

I have some experience in this area. JSON Logic let’s you serialize rules in JSON and there implementations in multiple languages. Another option would be Remote.Linq which allows you to serialize a LINQ expression tree to JSON.

Source generators are really great, but can't be used during run time, like emit can. For example, code generators are good for generating boiler plate code during compile time like this. But emit can be used during run time for things like this.

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)?