General
-
Implementation of delays and timeouts
An article or even included implementation showing how delays or timeouts can be implemented.
40 votes -
All state machine execution to be persisted and later restored
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
30 votes -
Data-driven state machine support
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...
27 votes -
Visual Studio 2010 Designer support
It will be nice to be able to design and visualise the state map using Visual Studio Designer.
23 votes -
Allow easy visualisation of states using yUML :)
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).
20 votes -
Validation, assertion if not all states are taken care of
Something like Automapper's AssertConfigurationIsValid()
http://automapper.codeplex.com/wikipage?title=Getting%20Started&referringTitle=Documentation
Feasible?
13 votes -
Port to .NET Micro Framework 4.1
It would be cool to run your state machine framework on little microcontrollers!
10 votes -
6 votes
-
Use a DSL to generate code
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
4 votes -
3 votes
