pmilet.DomainEvents 1.1.1

.NET Core 1.1 .NET Standard 2.0 .NET Framework 4.5.2
There is a newer version of this package available.
See the version list below for details.
NuGet\Install-Package pmilet.DomainEvents -Version 1.1.1
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
dotnet add package pmilet.DomainEvents --version 1.1.1
<PackageReference Include="pmilet.DomainEvents" Version="1.1.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add pmilet.DomainEvents --version 1.1.1
#r "nuget: pmilet.DomainEvents, 1.1.1"
#r directive can be used in F# Interactive, C# scripting and .NET Interactive. Copy this into the interactive tool or source code of the script to reference the package.
// Install pmilet.DomainEvents as a Cake Addin
#addin nuget:?package=pmilet.DomainEvents&version=1.1.1

// Install pmilet.DomainEvents as a Cake Tool
#tool nuget:?package=pmilet.DomainEvents&version=1.1.1

Purpose

The purppose of this library is to simplify the development of applications that use the Domain Event design pattern. This library is based on an article from Jimmy Boggard A better domain events pattern..

Domain Events

Martin Fowlers defines the domainEvent DDD pattern as: Domain Events captures the memory of something interesting which affects the domain. The essence of a Domain Event is that you use it to capture important things that happens into the domain and that can produce a change into the state of the application you are developing. Another good source of information is this chapter about Domain Events from the Microsoft ebook: .NET Microservices. Architecture for Containerized .NET Applications

1. Model your domain event

To create your DomainEvent class you could either inherit from the base Class DomainEvent or implement the IDomainEvent interface.

    /// <summary>
    /// Represents the play choosen by a player
    /// </summary>
    public class PlayMade : DomainEvent
    {
        public PlayMade(PlayerType player, PlayType play)
            : base( "PlayMade", "1.0")
        {
            Player = player;
            Play = play;
        }

        public PlayerType Player { get; private set; }
        public PlayType Play { get; private set; }

    }

2. Create an instance of the DomainEventDispatcher

From your business logic you can publish events or subscribe to events by means of a DomainEventDispatcher instance.

  // we create the domain event dispatcher and inject it into the objects of our domain model (normally done using a IoC container) 
  IDomainEventDispatcher dispatcher = new DomainEventDispatcher();
  Player j1 = new Player1(dispatcher);
  Player j2 = new Player2(dispatcher);
  Match match = new Match(dispatcher);
  Outcome outcome = new Outcome(dispatcher);

Note: a better option is to register the DomainEventDispatcher instance in your IoC container.

3. Trigger domain events from your business logic

To trigger an domain event immediately we should use the DomainEventDipatcher Publish<T> method:

  //publish an event notifying that the match ended and Player1 is the winner
  _dispatcher.Publish<MatchEnded>(new MatchEnded(PlayerType.Player1));

To add a delayed domain event we should use the Add<T> method :

  //delayed event to notify of the move choosen by the player
  _dispatcher.Add<PlayMade>(new PlayMade( _player, play ));

To trigger all the delayed domain events of a specific type we should use the Commit<T> method :

    //commit all registered delayed events
    _dispatcher.Commit<PlayMade>();

4. Respond to specific domain events from your business logic by subscribing to them

To subscribe to specific domain events we should inherit from the IHandleDomainEvents<T> interface and subscribe to the dispatcher instance (normally in the constructor).

    public class Outcome : HandleDomainEventsBase<MatchEnded>
    {
        PlayerType _lastWinner;
        public Outcome(IDomainEventDispatcher dispatcher):base(dispatcher)
        {}

        public override void HandleEvent(MatchEnded domainEvent)
        {
            _lastWinner = domainEvent.Winner;
        }
        
        public PlayerType LastWinner()
        {
            return _lastWinner;
        }

    }
    ```

### See a example app that uses domain events 
    
    To see a running sample take a look to the StonePaperScissors app or specflow functional tests from the [github](https://github.com/pmilet/domainevents) repo 
    



Product Versions
.NET net5.0 net5.0-windows net6.0 net6.0-android net6.0-ios net6.0-maccatalyst net6.0-macos net6.0-tvos net6.0-windows
.NET Core netcoreapp1.1 netcoreapp2.0 netcoreapp2.1 netcoreapp2.2 netcoreapp3.0 netcoreapp3.1
.NET Standard netstandard2.0 netstandard2.1
.NET Framework net452 net46 net461 net462 net463 net47 net471 net472 net48
MonoAndroid monoandroid
MonoMac monomac
MonoTouch monotouch
Tizen tizen40 tizen60
Xamarin.iOS xamarinios
Xamarin.Mac xamarinmac
Xamarin.TVOS xamarintvos
Xamarin.WatchOS xamarinwatchos
Compatible target framework(s)
Additional computed target framework(s)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.3.0 1,393 4/1/2019
1.2.0 675 2/16/2018
1.1.1 768 1/26/2018
1.1.0 800 1/23/2018
1.0.5 805 10/25/2017
1.0.4 635 10/22/2017
1.0.3 709 10/18/2017
1.0.1 1,088 10/1/2017
1.0.0 1,077 9/27/2017

target frameworks: netcoreapp1.1;netcoreapp2.0;netstandard2.0;net461;net452