EventFlow.SQLite 0.45.2877

Prefix Reserved
There is a newer version of this package available.
See the version list below for details.
dotnet add package EventFlow.SQLite --version 0.45.2877                
NuGet\Install-Package EventFlow.SQLite -Version 0.45.2877                
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.SQLite" Version="0.45.2877" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add EventFlow.SQLite --version 0.45.2877                
#r "nuget: EventFlow.SQLite, 0.45.2877"                
#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.SQLite as a Cake Addin
#addin nuget:?package=EventFlow.SQLite&version=0.45.2877

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

SQLite event store 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 9,061 9/7/2021
0.82.4684 507 8/30/2021
0.82.4659 533 6/17/2021
0.81.4483 852 12/14/2020
0.80.4377 673 10/1/2020
0.79.4216 751 5/13/2020
0.78.4205 658 5/11/2020
0.77.4077 979 12/10/2019
0.76.4014 874 10/19/2019
0.75.3970 722 9/12/2019
0.74.3948 972 7/1/2019
0.73.3933 747 6/11/2019
0.72.3914 736 5/28/2019
0.71.3834 792 4/17/2019
0.70.3824 771 4/11/2019
0.69.3772 891 2/12/2019
0.68.3728 914 12/3/2018
0.67.3697 955 10/14/2018
0.66.3673 982 9/28/2018
0.65.3664 943 9/22/2018
0.64.3598 1,037 8/27/2018
0.63.3581 925 8/7/2018
0.62.3569 891 7/5/2018
0.61.3524 1,012 6/26/2018
0.60.3490 997 6/18/2018
0.59.3396 1,064 5/23/2018
0.58.3377 1,067 5/13/2018
0.57.3359 1,125 4/30/2018
0.56.3328 1,030 4/24/2018
0.55.3323 989 4/24/2018
0.54.3261 969 2/25/2018
0.53.3204 1,018 1/25/2018
0.52.3178 961 11/2/2017
0.51.3155 964 10/25/2017
0.50.3124 959 10/21/2017
0.49.3031 986 9/7/2017
0.48.2937 991 7/11/2017
0.47.2894 985 6/28/2017
0.46.2886 1,046 5/29/2017
0.45.2877 1,042 5/28/2017
0.44.2832 1,009 5/12/2017
0.43.2806 1,031 5/5/2017
0.42.2755 981 5/2/2017
0.41.2727 969 4/27/2017
0.40.2590 1,021 3/30/2017
0.39.2553 1,015 1/16/2017
0.38.2454 1,019 12/2/2016
0.37.2424 1,253 11/8/2016
0.36.2315 988 10/18/2016
0.35.2247 1,012 9/6/2016
0.34.2221 1,037 8/23/2016
0.33.2190 1,038 8/16/2016
0.32.2163 1,075 7/4/2016
0.31.2106 1,075 6/30/2016
0.30.2019 1,403 6/16/2016
0.29.1973 1,040 4/19/2016
0.28.1852 1,083 4/5/2016
0.27.1765 1,380 2/25/2016
0.26.1714 1,072 2/20/2016

Breaking: Asynchronous subscribers are now **disabled by default**, i.e.,
any implementations of `ISubscribeAsynchronousTo<,,>` wont get invoked
unless enabled
```
eventFlowOptions.Configure(c => IsAsynchronousSubscribersEnabled = true);
```
the `ITaskRunner` has been removed and asynchronous subscribers are now
invoked using a new scheduled job that's scheduled to run right after the
domain events are emitted. Using the `ITaskRunner` led to unexpected task
terminations, especially if EventFlow was hosted in IIS. If enabling
asynchronous subscribers, please _make sure_ to configure proper job
scheduling, e.g. by using the `EventFlow.Hangfire` NuGet package. The default
job scheduler is `InstantJobScheduler`, which executes jobs _synchronously_,
giving a end result similar to that of synchronous subscribers
Breaking: `InstantJobScheduler`, the default in-memory scheduler if nothing
is configured, now swallows all job exceptions and logs them as errors. This
ensure that the `InstantJobScheduler` behaves as any other out-of-process
job scheduler