Config based usage of Stateless?

[Jaim Zuber]

All,

My client is looking to use a State Machine to create a pluggable
workflow for their application. The app will be hosted in a different
environment for each customer and each customer may have a unique
workflow requirement. We are looking at ways to add customers as
simply as possible.

We were initially were attracted to the Boo interface of the Simple
State Machine project. The thinking was the Boo Based DSL would be an
easy way to wire up an environment for a new customer without
recompiling the main application. That said, we like the additional
features of Stateless and would prefer not to use Abandon-ware.

I'm wondering if any users of Stateless have found patterns to create
low-friction configuration changes for use in multiple environments.
If so, I'd like to hear about approaches that have worked well.

Any advice?


Thanks,

Jaim

[Grant BlahaErath]

I originally bolted a xaml representation to stateless using a proxy construction pattern. I later switched to storing the .cs and compiling them into temp assemblies using csc because the symantics we evolving to a language anyway.

Two ideas that worked well for me at least.