I also faced this dilemma about two years ago, since it was something simple enough, I didnβt want to go overboard, and time limited, I ended up creating something using an individual interpretation of logic for analysis ==, eg,! =,>, etc., using Linq and the strategy template as the basis of the rule evaluation mechanism
Although if you know the Windows Workflow Foundation, then, apparently, you can use the mechanism of your rules without actually using WF
Jason source share