Stratara.ServiceDefaults.AspNetCore 4.0.3

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

Stratara.ServiceDefaults.AspNetCore

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

License: MIT.

ASP.NET Core extensions on top of Stratara.ServiceDefaults. Reference from every API host.

What's in the box

Extension Purpose
AddDefaultHealthChecks Registers a self-tagged health check that always reports Healthy + tags it as live so the /alive predicate can filter on it.
MapDefaultEndpoints Maps /health (full health-check report) and /alive (only the live-tagged checks).
ConfigureAspNetOpenTelemetry Wires ASP.NET Core request instrumentation on metrics + tracing; filters out the health-check + aliveness endpoints from traces so they don't pollute the request stream.

Quick start

builder.ConfigureOpenTelemetry();                  // from Stratara.ServiceDefaults
builder.ConfigureAspNetOpenTelemetry();            // from this package
builder.AddDefaultHealthChecks();
builder.ConfigureSerilog();                        // from Stratara.ServiceDefaults

var app = builder.Build();
app.MapDefaultEndpoints();

Dependencies

  • Stratara.ServiceDefaults — base ConfigureOpenTelemetry and shared endpoint constants.
  • OpenTelemetry.Extensions.Hosting + OpenTelemetry.Instrumentation.AspNetCore.
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

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
4.0.3 52 9/3/2026
4.0.2 156 9/3/2026
4.0.1 94 9/2/2026
4.0.0 154 8/31/2026
4.0.0-preview.1 43 8/31/2026
3.4.0 123 8/28/2026
3.3.0 96 8/25/2026
3.2.3 92 8/22/2026
3.2.2 100 8/14/2026
3.2.1 456 8/2/2026
3.2.0 120 7/18/2026
3.1.7 117 7/1/2026
3.1.6 526 6/22/2026
3.1.5 116 6/22/2026
3.1.4 127 6/15/2026
3.1.3 121 6/10/2026
3.1.2 130 6/5/2026
3.1.1 202 6/1/2026
3.1.0 120 5/30/2026
3.0.23 116 5/28/2026

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.