Stratara.Contracts 4.0.3

Prefix Reserved
There is a newer version of this package available.
See the version list below for details.
dotnet add package Stratara.Contracts --version 4.0.3
                    
NuGet\Install-Package Stratara.Contracts -Version 4.0.3
                    
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.Contracts" Version="4.0.3" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Stratara.Contracts" Version="4.0.3" />
                    
Directory.Packages.props
<PackageReference Include="Stratara.Contracts" />
                    
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.Contracts --version 4.0.3
                    
#r "nuget: Stratara.Contracts, 4.0.3"
                    
#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.Contracts@4.0.3
                    
#: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.Contracts&version=4.0.3
                    
Install as a Cake Addin
#tool nuget:?package=Stratara.Contracts&version=4.0.3
                    
Install as a Cake Tool

Stratara.Contracts

Derived. The behaviour described here is specified under openspec/specs/. Those specifications are the source; this page explains and illustrates them.

License: MIT.

Wire-level POCO contracts shared by every Stratara package. Pure data records — no runtime, no DI, no infrastructure deps. Safe to reference from any layer.

Contents

  • Messages/EventMessage, EventBundle, CommandEnvelope — the cross-process envelope shapes that messaging adapters (Stratara.Outbox.RabbitMQ etc.) serialise on and off the bus.
  • Requests/PagedRequest — shared pagination + sort record used by query handlers across the family.
  • Session/SessionContext — public data shape for actor/subject identity, correlation, causation, and connection routing. The ISessionContextProvider service abstraction lives in Stratara.Abstractions; the ASP.NET Core middleware that populates it lives in Stratara.Sessions.

Quick reference

// Build a CommandEnvelope outside the framework (rare, but supported)
var envelope = new CommandEnvelope(
    Id: Guid.CreateVersion7(),
    CommandJson: commandJson,
    CommandTypeName: typeof(MyCommand).AssemblyQualifiedName!,
    SessionContextJson: sessionContextJson);

Dependencies

None. Contracts is the lowest tier in the Stratara dependency graph.

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.
  • net10.0

    • No dependencies.

NuGet packages (9)

Showing the top 5 NuGet packages that depend on Stratara.Contracts:

Package Downloads
Stratara.Abstractions

Contract interfaces and POCO records for the Stratara CQRS / Event Sourcing framework — Mediator, EventSourcing, Persistence, Outbox, Messaging, Session, Security, Authorization. Library-safe, no EF Core or message-bus runtime.

Stratara.Sessions

ASP.NET Core middleware and provider for Stratara's Actor/Subject session model. Reads tenant and user from JWT claims (or X-Tenant-Id / X-Client-Id headers) and populates the ambient ISessionContextProvider for every request.

Stratara.Shared

Umbrella package for the Stratara framework — source-generated logger extensions for command flows, domain-event helpers, merge primitives, and the Tier-A/B abstractions surface re-exported as one transitive bundle.

Stratara.Projections

Projection runtime for the Stratara event-sourced stack — projection-handler discovery, change-set creation, update application, and projection manager. Sits between read-model repositories and the event-bundle dispatcher.

Stratara.Outbox.RabbitMQ

Outbox-pattern command and event dispatch for the Stratara event-sourced stack — RabbitMQ IMessageBus implementation, retry worker, mediator command worker, and Redis-coordinated projection-replay state. Azure Service Bus support ships as the sibling Stratara.Outbox.AzureServiceBus package.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
4.4.0 39 9/27/2026
4.3.1 213 9/25/2026
4.3.0 531 9/23/2026
4.2.0 356 9/18/2026
4.1.1 361 9/16/2026
4.1.0 291 9/16/2026
4.0.4 1,143 9/14/2026
4.0.3 413 9/3/2026
4.0.2 816 9/3/2026
4.0.1 438 9/2/2026
4.0.0 870 8/31/2026
4.0.0-preview.1 163 8/31/2026
3.4.0 393 8/28/2026
3.3.0 550 8/25/2026
3.2.3 378 8/22/2026
3.2.2 928 8/14/2026
3.2.1 929 8/2/2026
3.2.0 357 7/18/2026
3.1.7 768 7/1/2026
3.1.6 760 6/22/2026
Loading failed

Three fixes to the same complaint: a host composed exactly as the documentation describes did not
start. Each one was a registration the composites assumed somebody else had made — a tracer, a unit
of work, a Redis connection — and each is now made by the registration that needs it. Nothing that
already worked changes: every fix defers to a registration the host makes itself, in either order,
so the lines a working host added to get past these gaps can simply be deleted. Additive on every
published surface.

### Fixed

- **A host without Redis starts and dispatches.** Every composite that carries a dispatcher
 registered the projection-replay state, and its only implementation took a Redis connection that
 no composite registers, so a host composed as documented failed at its first dispatch unless it
 also ran Redis and called `AddCaching()`. `AddProjectionReplayState()` now chooses at first
 resolution: with a registered `IConnectionMultiplexer` the Redis-backed state as before, without
 one an in-process state with the same lease semantics — and a warning, once at start-up
 (`104_012`), that replay coordination is confined to that process, so a replay requested there
 suppresses publication there only. A deployment whose replay must reach several hosts registers
 the shared connection, in either order. Redis-backed hosts observe no change.
- **Registering a store context now registers its unit of work.**
 `AddNpgsqlWriteDbContextFactory<T>()` registered the context factory, the context and the default
 connection resolver but not the `IWriteUnitOfWork` that the event source, the outbox dispatcher and
 the command worker take from the container — and nothing else in the published packages did, so a
 host composed exactly as documented failed at its first command with a dependency-injection error.
 The write registration now try-adds a scoped `IWriteUnitOfWork` over its context, and
 `AddNpgsqlReadDbContextFactory<T>()` try-adds `IProjectionsUnitOfWork` and `IReadUnitOfWork`
 likewise. A unit of work the host registers itself, before or after, is still the one used; a
 hand-written registration can simply be deleted.
- **`AddMediator()` no longer requires the host to register an OpenTelemetry `Tracer`.** The
 mediator traces every dispatch and obtained its tracer from the host, but nothing registered one,
 so a host that called `AddMediator()` and nothing else failed at the first resolve of `IMediator`.
 `AddMediator()` now registers a fallback that emits the dispatch spans from the framework's
 `Stratara.Application` activity source — a host that subscribes to framework telemetry sees them,
 a host that subscribes to nothing pays for nothing. A `Tracer` the host registers, before or after
 `AddMediator()`, is still the one used, so no existing host changes behaviour; the registration
 line can simply be deleted. The samples, the README and the package README no longer carry it.