EventFlow.Hangfire 0.18.1181

The ID prefix of this package has been reserved for one of the owners of this package by NuGet.org. Prefix Reserved
.NET Framework 4.5.1
There is a newer version of this package available.
See the version list below for details. 
dotnet add package EventFlow.Hangfire --version 0.18.1181
NuGet\Install-Package EventFlow.Hangfire -Version 0.18.1181
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="EventFlow.Hangfire" Version="0.18.1181" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add EventFlow.Hangfire --version 0.18.1181
#r "nuget: EventFlow.Hangfire, 0.18.1181"
#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 EventFlow.Hangfire as a Cake Addin
#addin nuget:?package=EventFlow.Hangfire&version=0.18.1181

// Install EventFlow.Hangfire as a Cake Tool
#tool nuget:?package=EventFlow.Hangfire&version=0.18.1181

Hangfire job scheduling support for EventFlow

Product 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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

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
0.83.4713 42,417 9/7/2021
0.82.4684 387 8/30/2021
0.82.4659 4,091 6/17/2021
0.81.4483 2,409 12/14/2020
0.80.4377 1,459 10/1/2020
0.79.4216 16,311 5/13/2020
0.78.4205 481 5/11/2020
0.77.4077 14,948 12/10/2019
0.76.4014 1,497 10/19/2019
0.75.3970 1,557 9/12/2019
0.74.3948 1,128 7/1/2019
0.73.3933 753 6/11/2019
0.72.3914 2,627 5/28/2019
0.71.3834 809 4/17/2019
0.70.3824 672 4/11/2019
0.69.3772 954 2/12/2019
0.68.3728 7,097 12/3/2018
0.67.3697 1,904 10/14/2018
0.66.3673 887 9/28/2018
0.65.3664 4,200 9/22/2018
0.64.3598 4,013 8/27/2018
0.63.3581 1,002 8/7/2018
0.62.3569 5,588 7/5/2018
0.61.3524 1,067 6/26/2018
0.60.3490 1,139 6/18/2018
0.59.3396 1,052 5/23/2018
0.58.3377 1,123 5/13/2018
0.57.3359 1,162 4/30/2018
0.56.3328 1,074 4/24/2018
0.55.3323 1,061 4/24/2018
0.54.3261 949 2/25/2018
0.53.3204 976 1/25/2018
0.52.3178 1,652 11/2/2017
0.51.3155 932 10/25/2017
0.50.3124 939 10/21/2017
0.49.3031 961 9/7/2017
0.48.2937 1,152 7/11/2017
0.47.2894 1,723 6/28/2017
0.46.2886 1,264 5/29/2017
0.45.2877 1,027 5/28/2017
0.44.2832 1,203 5/12/2017
0.43.2806 1,025 5/5/2017
0.42.2755 990 5/2/2017
0.41.2727 952 4/27/2017
0.40.2590 4,086 3/30/2017
0.39.2553 1,030 1/16/2017
0.38.2454 1,143 12/2/2016
0.37.2424 1,239 11/8/2016
0.36.2315 1,821 10/18/2016
0.35.2247 1,233 9/6/2016
0.34.2221 991 8/23/2016
0.33.2190 1,005 8/16/2016
0.32.2163 1,040 7/4/2016
0.31.2106 1,040 6/30/2016
0.30.2019 1,363 6/16/2016
0.29.1973 1,046 4/19/2016
0.28.1852 1,024 4/5/2016
0.27.1765 4,485 2/25/2016
0.26.1714 1,062 2/20/2016
0.25.1695 1,052 2/15/2016
0.24.1563 1,419 1/25/2016
0.23.1470 1,589 12/5/2015
0.22.1393 1,953 11/19/2015
0.21.1312 1,163 10/26/2015
0.20.1274 1,037 10/22/2015
0.19.1225 1,063 10/19/2015
0.18.1181 1,187 10/7/2015
0.17.1134 1,129 9/28/2015
0.16.1120 1,110 9/27/2015
0.15.1057 1,094 9/24/2015
0.14.1051 1,111 9/23/2015

POTENTIAL DATA LOSS for the **files event store**: The EventFlow
internal functionality regarding event stores has been refactored resulting
in information regarding aggregate names being removed from the event
persistence layer. The files based event store no longer stores its events in
the path `[STORE PATH]\[AGGREGATE NAME]\[AGGREGATE ID]\[SEQUENCE].json`, but
in the path `[STORE PATH]\[AGGREGATE ID]\[SEQUENCE].json`. Thus if you are
using the files event store for tests, you should move the events into the
new file structure. Alternatively, implement the new `IFilesEventLocator` and
provide your own custom event file layout.
Breaking: Event stores have been split into two parts, the `IEventStore`
and the new `IEventPersistence`. `IEventStore` has the same interface before
but the implementation is now no longer responsible for persisting the events,
only converting and serializing the persisted events. `IEventPersistence`
handles the actual storing of events and thus if any custom event stores have
been implemented, they should implement to the new `IEventPersistence`
instead.
New: Added `IEntity`, `IEntity<>` and an optional `Entity<>` that developers
can use to implement DDD entities.