QuickStateMachine allows you to handle state machine actions by writing one class per action.

NuGet -- Install-Package QuickStateMachine

Example class:

[StateMachineExitState("InitialTestState", typeof(Tester))]
    internal class TestExitStateHandler : StateHandlerBase<Tester>
    {
        public override Task ExecuteAsync(Tester target)
        {
        }
    }

It will triggered when state of object of class Tester is changed from InitialTestState to something else. Object of class Tester will be passed to execute method where you can define your logic for exiting state.

You must derive from class StateHandlerBase where T is class of object it will manage. Not that atribute has also typeof(T) paramater. Attribute and base class type must be the same.

Other attributes are:

[StateMachineTransition("from", "to", typeof(T))]

Triggered when object transitions from state "from" to state "to".

[StateMachineEnterState("to", typeof(T))]

Triggers when object is entering state "to".

QuickStateMachine will automaticaly lookup for handlers, but there is also a chance that it wont find anything. In that case call:

StateMachineExecutor.Current.InitializeWithAssemblyAsync(assembly);

It takes assembly in which handlers are defined as parameter.

Next step is to make sure to call

StateMachineExecutor.Current.InitialStateAsync(object, state);

for every object that will be handled with state machine.

For changing state call:

StateMachineExecutor.Current.ChangeStateAsync(object, state);

It will handle all actions defined with Handler classes for given object.

Remember that state is defined for each object, not class.