5.1.0: - completely redesigned the state machine definition API. You can now define a state machine definition and then spawn state machine instances from the definition. This speeds up creation of state machines from a static definition for example in ASP.NET requests. The initial state is set at definition time (on the definition) and not on the state machine anymore. The interfaces of the extensions had to be changed, too. For details see https://github.com/appccelerate/statemachine/pull/51, https://github.com/appccelerate/statemachine/pull/52 and https://github.com/appccelerate/statemachine/pull/53 - Loading and saving the state machinbe now includes the queued events. The whole internal state holding was redesigned to be in a single place. Details see https://github.com/appccelerate/statemachine/pull/53 - fixed that Fire on AsyncActiveStateMachine could not complete on blocking ExecuteOnEntry. Details see https://github.com/appccelerate/statemachine/pull/49 - changed release pipeline of Appccelerate.StateMachine and lots of internal stuff

  4.4.0:
  - back to .net standard 1.0
  - fixed nuget package containing wrong assembly

  4.0.0:
  - adds AsyncPassiveStateMachine that supports async/await for transition actions, entry/exit actions, guards and save/load.
  - targets .net standard 1.3 to support async/await

  3.3.0:
  - fixed: wrong target framework was specified in nuget package. Now targets .net standard 1.0

  3.2.0:
  - targets now .net standard 1.0 so you can use the state machine almost anywhere .net exists
  - fixed a bug when passing a 'null' argument to the state machine