Stratara.EventSourcing.EntityFrameworkCore 3.1.2

.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher. 
dotnet add package Stratara.EventSourcing.EntityFrameworkCore --version 3.1.2
                    


                    

                
NuGet\Install-Package Stratara.EventSourcing.EntityFrameworkCore -Version 3.1.2
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="Stratara.EventSourcing.EntityFrameworkCore" Version="3.1.2" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="Stratara.EventSourcing.EntityFrameworkCore" Version="3.1.2" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Stratara.EventSourcing.EntityFrameworkCore" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add Stratara.EventSourcing.EntityFrameworkCore --version 3.1.2
                    


                    

                
#r "nuget: Stratara.EventSourcing.EntityFrameworkCore, 3.1.2"
#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. 
#:package Stratara.EventSourcing.EntityFrameworkCore@3.1.2
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=Stratara.EventSourcing.EntityFrameworkCore&version=3.1.2
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Stratara.EventSourcing.EntityFrameworkCore&version=3.1.2
                    


                            Install as a Cake Tool

Stratara.EventSourcing.EntityFrameworkCore

License: FSL-1.1-MIT (Functional Source License — source-available; converts to MIT after 2 years). Not OSI-approved OSS.

EF Core persistence for the Stratara event-sourced stack — PostgreSQL flavoured via Npgsql + pgvector. Bundles four previously-separate Stratara projects into one NuGet because they always ship together:

Folder Contents Old csproj
EntityFrameworkCore/ shared EF conventions, value generators, IDbContext / IReadDbContext / IWriteDbContext / ITenantScopedDbContext / IIdentityDbContext, UnitOfWork base, DefaultDbResolver, NpgsqlDbContextServiceCollectionExtensions, DbContextMigrationUtility Stratara.EntityFrameworkCore
WriteStore/ WriteDbContext, WriteUnitOfWork, event-stream/snapshot/event-chain/command-audit/outbox repositories + entity configurations Stratara.EventSourcing.EntityFrameworkCore.WriteStore
ReadStore/ ReadDbContext, ReadUnitOfWork, ProjectionsUnitOfWork, Tenant repository, projection entity configurations Stratara.EventSourcing.EntityFrameworkCore.ReadStore
IdentityStore/ Generic ASP.NET Identity IdentityDbContext + marker Stratara.EventSourcing.EntityFrameworkCore.IdentityStore

Namespaces are unchanged from the pre-fold layout (Stratara.EntityFrameworkCore, Stratara.EventSourcing.EntityFrameworkCore.WriteStore, Stratara.EventSourcing.EntityFrameworkCore.ReadStore, Stratara.EventSourcing.EntityFrameworkCore.IdentityStore) so consumer using directives don't change.

Why folded

WriteStore-without-ReadStore is not a real use case. EF conventions + value generators + UnitOfWork primitives are foundational for every other store. ASP.NET Identity glue follows the same EF Core conventions. Splitting into 4 NuGets that always ship together adds version-management noise (4× <PackageVersion> to keep in sync, transitive-resolution risk) without any consumer benefit.

If your application doesn't use ASP.NET Identity, simply don't reference IdentityDbContext-derived types — the rest of the package works without them.

Quick start

// In your AppHost / Worker / Web project:
builder.Services.AddNpgsqlWriteStore<MyAppWriteDbContext>(builder.Configuration);
builder.Services.AddNpgsqlReadStore<MyAppReadDbContext>(builder.Configuration);

Then derive MyAppWriteDbContext : Stratara.EventSourcing.EntityFrameworkCore.WriteStore.WriteDbContext and MyAppReadDbContext : Stratara.EventSourcing.EntityFrameworkCore.ReadStore.ReadDbContext.

Dependencies

  • Stratara.Projections — for projection types used by ProjectionsUnitOfWork.
  • Stratara.Shared — for diagnostics + abstractions + resilience.
  • Npgsql.EntityFrameworkCore.PostgreSQL, EFCore.NamingConventions, Microsoft.AspNetCore.Identity.EntityFrameworkCore, Microsoft.EntityFrameworkCore, Pgvector.EntityFrameworkCore.
Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (3)

Showing the top 3 NuGet packages that depend on Stratara.EventSourcing.EntityFrameworkCore:

Package Downloads
Stratara.Infrastructure

Infrastructure glue for the Stratara framework — authorization decorators, configuration providers, and DI composition helpers that wire Mediator, Outbox, Identity, and EF Core into a hosted app.
Stratara.EventSourcing.WorkerDefaults

Worker-host wiring composites for the Stratara event-sourced stack. IHostApplicationBuilder extensions (AddBackendServices, AddCommandWorkerServices, AddEventProjectionWorkerServices, AddSagaWorkerServices, AddOutboxWorkerServices) bundle the per-concern DI calls so each worker host opts in with one line.
Stratara.Testing.EntityFrameworkCore

Spin up the real Stratara event-sourcing write stack (EventSource, aggregation, snapshots, the EF Core write store) against a shared in-memory SQLite database in one call — production code paths, no Postgres, no Docker. Builds on Stratara.Testing's in-memory doubles.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
3.1.2 58 6/5/2026
3.1.1 204 6/1/2026
3.1.0 116 5/30/2026
3.0.23 121 5/28/2026

### Added

- **New package `Stratara.Testing`** — test doubles and assertion helpers so consumers can
 unit-test Stratara-based code without Postgres or RabbitMQ testcontainers. Reference it from
 test projects only.
 - `AggregateTestHarness<T>` + `Aggregate.Rehydrate<T>(...)` — given/when/then rehydration of an
   aggregate from events using the same reflection-based `Apply(...)` dispatch as the production
   aggregation service. It throws on an event with no matching `Apply` overload so a forgotten or
   mistyped overload fails the test; opt back into the production-lenient skip with
   `IgnoringUnmappedEvents()`.
 - `InMemoryKeyStore` — an `IKeyStore` that mints random 256-bit DEKs per `KeyScope` and supports
   rotation / revocation / scope-erasure without a master KEK or key file.
 - `TestBlobEncryptor.CreateAesGcm()` — the real AES-GCM `ISecureBlobEncryptor` over an
   `InMemoryKeyStore`, so blob round-trips exercise production encryption.
 - `InMemoryMessageBus` — an `IMessageBus` with synchronous in-process dispatch and a `Published`
   list for assertions.
 - `TestSessionContext` / `TestSessionContextProvider` — preset Actor/Subject `SessionContext`
   values and an `ISessionContextProvider` double.
 - `TestTenants.Of("acme")` — stable, deterministic tenant/user ids from readable slugs.
   `TestSessionContext` sets both correlation and causation ids so the context can drive
   event-store writes.
 - `TestEvent.Create(payload, ...)` — wrap an event payload in `IEvent<T>` with realistic
   metadata; `ProjectionTester.HandleAsync(projection, event)` — invoke a projection's private
   `HandleAsync` handler directly to unit-test it against mocked repositories.
- **New package `Stratara.Testing.EntityFrameworkCore`** — spins up the **real** event-sourcing
 write stack (`IEventSource`, `IAggregationService`, snapshots, the EF Core write store) against a
 shared in-memory SQLite database in one call, so tests exercise production code paths without
 Postgres or Docker. Reference it from test projects only.
 - `EventStoreTestHost.Create(...)` — owns the SQLite connection + service provider; exposes
   `ExecuteAsync(IEventSource)`, `AggregateAsync<T>(streamId)`, the preset `Session`, and the
   recording `Outbox`.
 - `AddStrataraTestingEventStore<TWriteDbContext>(connection, tenantId)` — the lower-level DI
   extension; `StrataraTestWriteDbContext` — a ready-made concrete write context;
   `RecordingEventBundleOutboxDispatcher` — captures emitted bundles for assertions.
 - The lockstep family grows from 22 to 24 packable packages.