An article or even included implementation showing how delays or timeouts can be implemented.

The code-driven state machine functionality could be used as a kernel to drive an XML, text or database-driven state machine framework.

It would be especially interesting to integrate this with Visual Studio's drawing surface support...

Would be great to persist the FSM execution somewhere automatically, then restore it later. This would be very handy for my current task of modelling an ordering system

It will be nice to be able to design and visualise the state map using Visual Studio Designer.

This would need to be an addin or something, but it would be nice to have a way of visualising states as a diagram. Perhaps using http://yuml.me activity diagrams (until State diagrams are implemented).

Something like Automapper's AssertConfigurationIsValid()

http://automapper.codeplex.com/wikipage?title=Getting%20Started&referringTitle=Documentation

Feasible?

It would be cool to run your state machine framework on little microcontrollers!

Move source code hosting to github so that it easier for people to fork/contribute changes to the project.

Thank you! It's awesome!

I have a need to log the entry/exit of the OnEntry and OnExit methods. It would be usefull if the framework provided a mechanism for adding these kind of aspects.

is there sample code somewhere?

Flit uses a Dot-like text-based DSL. I Think it would be interesting to have the same feature : http://flit.codeplex.com/wikipage?title=Dot&referringTitle=Home

Can we handle sub workflow ? I mean if there is a sub workflow attached to specific step then how can we handle it ?

Or if anyone know how to do it with existing framework please tell me.