Last post Apr 18, 2011 02:48 PM by Xequence
Mar 11, 2011 08:13 AM|Xequence|LINK
I have been assigned the task to create a rules engine with another programmer for a company. They want it totally dynamic (parameterized sql type dynamic, no inline or any wishy washy coding practices). So I have ended up with no idea what to really aim
at since this is the first time for this type of project. I am hoping someone has some ideas if they have experience this before. I am thinking of going in this direction.
Any advice would be greatly appreciated!
Mar 11, 2011 08:30 AM|rtpHarry|LINK
I think workflow sounds like a good way to abstract away a general problem.
Just wanted to give you heads up that WF has changed quite dramatically since when that article was written in 2007 so if you are working with .net 4.0 then you will probably want to find a newer article.
Mar 11, 2011 10:24 AM|Xequence|LINK
Great, thanks. I hope to find more relevant information soon.
Mar 11, 2011 08:08 PM|Xequence|LINK
So far this has been the only thing available. Not that popular of a subject, but I think it is great so far.
Mar 11, 2011 09:48 PM|Xequence|LINK
Why is this not a more seen application?
Create basic WCF client and service.
New material though.
Apr 12, 2011 07:07 PM|Xequence|LINK
I am keeping prototype in mind when I am developing this. So far, I have side stepped into generating an event driven application using my very limited knowledge of delegates and events. Almost took an even wider side step into the realm of generating dynamic
linq that created generated where clauses. Now I am almost 360 degrees back to using WF and WPF and WCF to generate a rule engine.
Would event driven logic be the wisest path to go? Or would WF give more flexibility and reusability?
I only hope that a user can understand how it will work.
Apr 18, 2011 09:36 AM|atconway|LINK
I am not an avid Workflow user, but I sat in on a class a few weeks back at CodeCamp which contained several heavy users including the instructor, and this was told to be the defacto literature on WF in .NET Framework 4.0:
Pro WF: Windows Workflow in .NET 4.0:
It was mentioned that there were not a lot of WF 4.0 books and this was the best one available. Of course you can always visit Microsoft's source of documentation on WF 4.0 listed below:
Windows Workflow is not an ASP.NET product or technology. Not to say you can't create ASP.NET applications using WF, but it seems to be a specialized field of .NET, so you may want to seek out forums specific to the technology if you get deep into it. The
MSDN forum for WF is below:
NET 4: Windows Workflow Foundation:
Now from a design pattern approach, there are some techniques you can employ to help with organizing and chaining together rules. A good example of this is sing the 'Specification Pattern'. I recommend watching the following video that will help show you
how to do this:
Learning the Specification Pattern:
Hope this helps!
Apr 18, 2011 02:48 PM|Xequence|LINK
Too bad this project is scoped at 800 hours otherwise I would love to look into that. :)
Good advice and a few of the videos gave me insite to chaining.