AggregateSourceAsync 1.0.0-alpha0002

This is a prerelease version of AggregateSourceAsync.
There is a newer prerelease version of this package available.
See the version list below for details.
dotnet add package AggregateSourceAsync --version 1.0.0-alpha0002
NuGet\Install-Package AggregateSourceAsync -Version 1.0.0-alpha0002
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.
<PackageReference Include="AggregateSourceAsync" Version="1.0.0-alpha0002" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add AggregateSourceAsync --version 1.0.0-alpha0002
#r "nuget: AggregateSourceAsync, 1.0.0-alpha0002"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install AggregateSourceAsync as a Cake Addin
#addin nuget:?package=AggregateSourceAsync&version=1.0.0-alpha0002&prerelease

// Install AggregateSourceAsync as a Cake Tool
#tool nuget:?package=AggregateSourceAsync&version=1.0.0-alpha0002&prerelease

AggregateSourceAsync

This project differs from AggregateSource upon which is it heavily based. The async model has been enhanced to allow cancellation tokens to be passed and this is most useful when paired with the AggregateSourceAsync.NEventStoreAsync project which correctly exposes asynchronous operations.

The project is dependent upon .NET 4.6 or .NET Standard 2.0.

Gitter

This library/code provides lightweight infrastructure for doing eventsourcing using aggregates. It's not a framework, and it never will be. Period.

The preferred way of using it, is copying it into your project and getting rid of all the cruft you don't need. That said, there are NuGet packages available for those of you that are pressed for time and don't mind following the prescribed recipe.

It's well suited for those scenarios where multiple aggregates need to collaborate and is lenient to saving multiple aggregates in one go should your underlying store allow you to do so or your problem domain require you to do so. Of course, nothing is holding you back from throwing when multiple aggregates have been changed. I just think this shouldn't interfere with the programming model you use. Granted, for affecting only one aggregate, there are simpler solutions and to be honest, what I bring you here is in no way unique:

Core

Contains the core types that you will want interact with when building your domain model. A more thorough explanation can be found here

Testing

Helps you write test specifications, using a simple, codified statechart and a fluent syntax. A more thorough explanation can be found here

License

Licensed using a BSD 3-Clause License. See License.txt for more details

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net46 is compatible.  net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.
  • .NETFramework 4.6

  • .NETStandard 2.0

NuGet packages (3)

Showing the top 3 NuGet packages that depend on AggregateSourceAsync:

Package Downloads
AggregateSourceAsync.Content.ExplicitRouting

AggregateSourceAsync is an async capable version of AggregateSource project.

AggregateSourceAsync.Content.ExplicitStateExplicitRouting

AggregateSourceAsync is an async capable version of AggregateSource project.

AggregateSourceAsync.NEventStoreAsync

Integration to allow the use of NEventStoreAsync with AggregateSourceAsync.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.0.0-alpha0007 852 1/16/2019
1.0.0-alpha0003 793 1/16/2019
1.0.0-alpha0002 529 1/15/2019

This package is similar to but incompatible with AggregateSource! Please check the release notes on github.