Stratara.Shared
4.4.4
Prefix Reserved
dotnet add package Stratara.Shared --version 4.4.4
NuGet\Install-Package Stratara.Shared -Version 4.4.4
<PackageReference Include="Stratara.Shared" Version="4.4.4" />
<PackageVersion Include="Stratara.Shared" Version="4.4.4" />
<PackageReference Include="Stratara.Shared" />
paket add Stratara.Shared --version 4.4.4
#r "nuget: Stratara.Shared, 4.4.4"
#:package Stratara.Shared@4.4.4
#addin nuget:?package=Stratara.Shared&version=4.4.4
#tool nuget:?package=Stratara.Shared&version=4.4.4
Stratara.Shared
Derived. The behaviour described here is specified under
openspec/specs/. Those specifications are the source; this page explains and illustrates them.
License: MIT.
Umbrella of shared utilities for the Stratara framework. Re-exports the Tier-A/B stack (Abstractions, Contracts, Diagnostics, Domain, Resilience, SessionContext) so consumers can pull one package and reach every common type.
Contents
- Source-generated
Logger*Extensionsfor command flows. The outbox, messaging, saga, and projection surfaces have since moved to the packages that own them (Stratara.Outbox.RabbitMQ,Stratara.Sagas,Stratara.Projections) — they keep theStratara.Shared.Diagnostics.Extensionsnamespace, which is why they can look like they still live here. - Domain-event helpers + merge primitives used across the framework.
- Re-export of every Tier-A/B Stratara public type via project-reference fan-out.
Quick reference
// One package reference reaches every Tier-A/B public type
using Stratara.Abstractions.Mediator; // ICommand, IQuery, IMediator
using Stratara.Contracts.Session; // SessionContext
using Stratara.Diagnostics; // ApplicationDiagnostics
// Source-generated logger extensions provided by Shared
logger.LogCommandWorkerStarted();
Dependencies
Transitively depends on every Tier-A/B package: Stratara.Abstractions, Stratara.Contracts, Stratara.Diagnostics, Stratara.Domain, Stratara.Resilience, Stratara.Sessions.
| Product | Versions 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. |
-
net10.0
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.11)
- Microsoft.Extensions.Logging.Abstractions (>= 10.0.11)
- Microsoft.Extensions.Options (>= 10.0.11)
- Microsoft.Extensions.Resilience (>= 10.9.0)
- OpenTelemetry.Api (>= 1.18.0)
- Stratara.Abstractions (>= 4.4.4)
- Stratara.Contracts (>= 4.4.4)
- Stratara.Diagnostics (>= 4.4.4)
- Stratara.Domain (>= 4.4.4)
- Stratara.Resilience (>= 4.4.4)
- Stratara.Sessions (>= 4.4.4)
NuGet packages (12)
Showing the top 5 NuGet packages that depend on Stratara.Shared:
| Package | Downloads |
|---|---|
|
Stratara.Identity.Core
Channel-agnostic identity primitives for the Stratara stack — login/claims/access-token records, sign-in / authentication-state / token-storage abstractions, and a typed HttpClient helper. Shared contract for web, mobile, and desktop hosts. |
|
|
Stratara.Identity.AspNetCore
Channel-agnostic ASP.NET Core identity wiring for the Stratara stack — AddAspNetIdentity and AddAspNetIdentityWithSignInManager extensions, IStrataraSignInManager wrapper, EF stores, i18n'd failure messages, optional passkey support, external-login OpenID Connect + JWT-bearer helpers, and hardened JIT external-login provisioning. Consumers wire their own AuthenticationStateProvider (Blazor Server, MAUI, etc.). |
|
|
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.EventSourcing.EntityFrameworkCore
EF Core persistence for the Stratara event-sourced stack on PostgreSQL — write-store, read-store, ASP.NET Identity store, shared conventions, value generators, and UnitOfWork primitives. Targets Npgsql; maps pgvector types for a model that uses them, and needs no database extension otherwise. |
|
|
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.4 | 160 | 10/10/2026 |
| 4.4.3 | 113 | 10/10/2026 |
| 4.4.2 | 519 | 10/2/2026 |
| 4.4.1 | 546 | 9/29/2026 |
| 4.4.0 | 278 | 9/27/2026 |
| 4.3.1 | 344 | 9/25/2026 |
| 4.3.0 | 525 | 9/23/2026 |
| 4.2.0 | 292 | 9/18/2026 |
| 4.1.1 | 289 | 9/16/2026 |
| 4.1.0 | 223 | 9/16/2026 |
| 4.0.4 | 1,079 | 9/14/2026 |
| 4.0.3 | 322 | 9/3/2026 |
| 4.0.2 | 737 | 9/3/2026 |
| 4.0.1 | 445 | 9/2/2026 |
| 4.0.0 | 809 | 8/31/2026 |
| 4.0.0-preview.1 | 122 | 8/31/2026 |
| 3.4.0 | 310 | 8/28/2026 |
| 3.3.0 | 457 | 8/25/2026 |
| 3.2.3 | 273 | 8/22/2026 |
| 3.2.2 | 848 | 8/14/2026 |
A one-fix release. On the Redis-backed replay state, a host could report a replay still active after it had ended
it, holding publication back for up to one refresh interval. Nothing else changes; no configuration or migration is
needed.
### Fixed
- **A host no longer reports a replay active after it ended the replay itself.** On the Redis-backed replay state, a
refresh that had read the marking just before the host's own deactivation could compare its generation before the
deactivation and write the field after it, leaving `IsReplayActive` true — and publication held back — until the
next refresh (`ProjectionReplay:RefreshSeconds`, default 5). The comparison and the write are now one step with the
transition. Present since 4.4.2.