EventFlow 0.14.1051
Prefix ReservedSee the version list below for details.
dotnet add package EventFlow --version 0.14.1051
NuGet\Install-Package EventFlow -Version 0.14.1051
<PackageReference Include="EventFlow" Version="0.14.1051" />
paket add EventFlow --version 0.14.1051
#r "nuget: EventFlow, 0.14.1051"
// Install EventFlow as a Cake Addin
#addin nuget:?package=EventFlow&version=0.14.1051
// Install EventFlow as a Cake Tool
#tool nuget:?package=EventFlow&version=0.14.1051
CQRS+ES framework
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET Framework | net451 is compatible. net452 was computed. net46 was computed. net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
-
- Newtonsoft.Json (>= 7.0.1)
NuGet packages (19)
Showing the top 5 NuGet packages that depend on EventFlow:
Package | Downloads |
---|---|
EventFlow.Sql
# EventFlow <img src="./icon-128.png" /> <a href="https://www.nuget.org/packages/EventFlow/"><img src="https://img.shields.io/nuget/v/EventFlow.svg?style=flat" /></a> <a href="https://gitter.im/rasmus/EventFlow?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge"><img src="https://badges.gitter.im/Join Chat.svg" /></a> <a href="https://github.com/eventflow/EventFlow/actions/workflows/ci.yml"><img src="https://github.com/eventflow/EventFlow/actions/workflows/ci.yml/badge.svg" /></a> NuGet feeds - Official releases: https://www.nuget.org/packages/EventFlow/ EventFlow is a basic CQRS+ES framework designed to be easy to use. Have a look at our [getting started guide](https://docs.geteventflow.net/GettingStarted.html), the [do’s and don’ts](https://docs.geteventflow.net/DosAndDonts.html) and the [FAQ](https://docs.geteventflow.net/FAQ.html). ## Features * **Easy to use**: Designed with sensible defaults and implementations that make it easy to create an example application * **Highly configurable and extendable**: EventFlow uses interfaces for every part of its core, making it easy to replace or extend existing features with custom implementation * **No use of threads or background workers** * **MIT licensed** Easy to understand and use license for enterprise |
|
EventFlow.AspNetCore
AspNetCore support for EventFlow |
|
EventFlow.DependencyInjection
Microsoft.Extensions.DependencyInjection support for EventFlow |
|
EventFlow.MongoDB
# EventFlow <img src="./icon-128.png" /> <a href="https://www.nuget.org/packages/EventFlow/"><img src="https://img.shields.io/nuget/v/EventFlow.svg?style=flat" /></a> <a href="https://gitter.im/rasmus/EventFlow?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge"><img src="https://badges.gitter.im/Join Chat.svg" /></a> <a href="https://github.com/eventflow/EventFlow/actions/workflows/ci.yml"><img src="https://github.com/eventflow/EventFlow/actions/workflows/ci.yml/badge.svg" /></a> NuGet feeds - Official releases: https://www.nuget.org/packages/EventFlow/ EventFlow is a basic CQRS+ES framework designed to be easy to use. Have a look at our [getting started guide](https://docs.geteventflow.net/GettingStarted.html), the [do’s and don’ts](https://docs.geteventflow.net/DosAndDonts.html) and the [FAQ](https://docs.geteventflow.net/FAQ.html). ## Features * **Easy to use**: Designed with sensible defaults and implementations that make it easy to create an example application * **Highly configurable and extendable**: EventFlow uses interfaces for every part of its core, making it easy to replace or extend existing features with custom implementation * **No use of threads or background workers** * **MIT licensed** Easy to understand and use license for enterprise |
|
EventFlow.Elasticsearch
Elasticsearch support for EventFlow |
GitHub repositories (2)
Showing the top 2 popular GitHub repositories that depend on EventFlow:
Repository | Stars |
---|---|
twzhangyang/RestAirline
DDD+CQRS+EventSourcing+Hypermedia API+ASP.NET Core 3.1+Masstransit+terraform+docker+k8s
|
|
OKTAYKIR/EventFlow.Example
DDD+CQRS+Event-sourcing examples using EventFlow following CQRS-ES architecture. It is configured with RabbitMQ, MongoDB(Snapshot store), PostgreSQL(Read store), EventStore(GES). It's targeted to .Net Core 2.2 and include docker compose file.
|
Version | Downloads | Last updated |
---|---|---|
1.0.5003-alpha | 5,472 | 6/21/2023 |
1.0.5002-alpha | 2,904 | 11/11/2022 |
1.0.5001-alpha | 2,201 | 3/15/2022 |
1.0.4748-alpha | 14,998 | 9/9/2021 |
1.0.4617-alpha | 1,630 | 6/11/2021 |
0.83.4713 | 854,734 | 9/7/2021 |
0.82.4684 | 7,819 | 8/30/2021 |
0.82.4659 | 34,057 | 6/17/2021 |
0.81.4483 | 154,285 | 12/14/2020 |
0.80.4377 | 50,147 | 10/1/2020 |
0.79.4216 | 117,529 | 5/13/2020 |
0.78.4205 | 5,631 | 5/11/2020 |
0.77.4077 | 93,235 | 12/10/2019 |
0.76.4014 | 33,649 | 10/19/2019 |
0.75.3970 | 12,234 | 9/12/2019 |
0.74.3948 | 23,669 | 7/1/2019 |
0.73.3933 | 9,318 | 6/11/2019 |
0.72.3914 | 11,468 | 5/28/2019 |
0.71.3834 | 14,698 | 4/17/2019 |
0.70.3824 | 6,674 | 4/11/2019 |
0.69.3772 | 16,999 | 2/12/2019 |
0.68.3728 | 45,816 | 12/3/2018 |
0.67.3697 | 12,710 | 10/14/2018 |
0.66.3673 | 8,413 | 9/28/2018 |
0.65.3664 | 10,424 | 9/22/2018 |
0.64.3598 | 10,093 | 8/27/2018 |
0.63.3581 | 8,983 | 8/7/2018 |
0.62.3569 | 35,030 | 7/5/2018 |
0.61.3524 | 6,282 | 6/26/2018 |
0.60.3490 | 5,203 | 6/18/2018 |
0.59.3396 | 5,956 | 5/23/2018 |
0.58.3377 | 4,986 | 5/13/2018 |
0.57.3359 | 5,711 | 4/30/2018 |
0.56.3328 | 4,476 | 4/24/2018 |
0.55.3323 | 4,609 | 4/24/2018 |
0.54.3261 | 6,000 | 2/25/2018 |
0.53.3204 | 4,528 | 1/25/2018 |
0.52.3178 | 5,247 | 11/2/2017 |
0.51.3155 | 4,101 | 10/25/2017 |
0.50.3124 | 4,168 | 10/21/2017 |
0.49.3031 | 6,718 | 9/7/2017 |
0.48.2937 | 5,337 | 7/11/2017 |
0.47.2894 | 4,816 | 6/28/2017 |
0.46.2886 | 7,644 | 5/29/2017 |
0.45.2877 | 4,272 | 5/28/2017 |
0.44.2832 | 4,128 | 5/12/2017 |
0.43.2806 | 2,322 | 5/5/2017 |
0.42.2755 | 4,916 | 5/2/2017 |
0.41.2727 | 4,803 | 4/27/2017 |
0.40.2590 | 8,002 | 3/30/2017 |
0.39.2553 | 5,045 | 1/16/2017 |
0.38.2454 | 4,893 | 12/2/2016 |
0.37.2424 | 5,078 | 11/8/2016 |
0.36.2315 | 6,071 | 10/18/2016 |
0.35.2247 | 5,005 | 9/6/2016 |
0.34.2221 | 4,746 | 8/23/2016 |
0.33.2190 | 4,521 | 8/16/2016 |
0.32.2163 | 4,686 | 7/4/2016 |
0.31.2106 | 4,494 | 6/30/2016 |
0.30.2019 | 4,851 | 6/16/2016 |
0.29.1973 | 6,248 | 4/19/2016 |
0.28.1852 | 4,551 | 4/5/2016 |
0.27.1765 | 7,901 | 2/25/2016 |
0.26.1714 | 4,527 | 2/20/2016 |
0.25.1695 | 3,881 | 2/15/2016 |
0.24.1563 | 4,256 | 1/25/2016 |
0.23.1470 | 4,907 | 12/5/2015 |
0.22.1393 | 4,761 | 11/19/2015 |
0.21.1312 | 4,013 | 10/26/2015 |
0.20.1274 | 3,825 | 10/22/2015 |
0.19.1225 | 3,746 | 10/19/2015 |
0.18.1181 | 4,100 | 10/7/2015 |
0.17.1134 | 3,971 | 9/28/2015 |
0.16.1120 | 3,878 | 9/27/2015 |
0.15.1057 | 3,948 | 9/24/2015 |
0.14.1051 | 3,919 | 9/23/2015 |
0.13.962 | 3,900 | 9/13/2015 |
0.12.891 | 3,687 | 9/4/2015 |
0.11.751 | 3,678 | 8/24/2015 |
0.10.642 | 3,453 | 8/17/2015 |
0.9.580 | 3,528 | 7/20/2015 |
0.8.560 | 3,351 | 5/29/2015 |
0.7.481 | 3,340 | 5/22/2015 |
0.6.456 | 3,177 | 5/18/2015 |
0.5.390 | 3,353 | 5/8/2015 |
0.4.353 | 3,222 | 5/5/2015 |
0.3.292 | 3,654 | 4/30/2015 |
Breaking: All `EventFlowOptions` extensions are now `IEventFlowOptions`
instead and `EventFlowOptions` implements this interface. If you have made
your own extensions, you will need to use the newly created interface
instead. Changed in order to make testing of extensions and classes
dependent on the EventFlow options easier to test
New: You can now bundle your configuration of EventFlow into modules that
implement `IModule` and register these by calling
`EventFlowOptions.RegisterModule(...)`
New: EventFlow now supports scheduled job execution via e.g. Hangfire. You
can create your own scheduler or install the new `EventFlow.Hangfire` NuGet
package. Read the jobs documentation for more details
New: Created the OWIN `CommandPublishMiddleware` middleware that can
handle publishing of commands by posting a JSON serialized command to
e.g. `/commands/ping/1` in which `ping` is the command name and `1` its
version. Remember to add authentication
New: Created a new interface `ICommand<TAggregate,TIdentity,TSourceIdentity>`
to allow developers to control the type of `ICommand.SourceId`. Using the
`ICommand<TAggregate,TIdentity>` (or Command<TAggregate,TIdentity>)
will still yield the same result as before, i.e., `ICommand.SourceId` being
of type `ISourceId`
New: The `AddDefaults(...)` now also adds the command type definition to the
new `ICommandDefinitonService`