Bsft.Scheduling.Correlation
2.2.0
dotnet add package Bsft.Scheduling.Correlation --version 2.2.0
NuGet\Install-Package Bsft.Scheduling.Correlation -Version 2.2.0
<PackageReference Include="Bsft.Scheduling.Correlation" Version="2.2.0" />
<PackageVersion Include="Bsft.Scheduling.Correlation" Version="2.2.0" />
<PackageReference Include="Bsft.Scheduling.Correlation" />
paket add Bsft.Scheduling.Correlation --version 2.2.0
#r "nuget: Bsft.Scheduling.Correlation, 2.2.0"
#:package Bsft.Scheduling.Correlation@2.2.0
#addin nuget:?package=Bsft.Scheduling.Correlation&version=2.2.0
#tool nuget:?package=Bsft.Scheduling.Correlation&version=2.2.0
Bsft.Scheduling.Correlation
The adapter between the Bsft.Correlation and Bsft.Scheduling families: a job enqueued while
handling a request carries that request's correlation id into an execution that may happen hours later.
Install
dotnet add package Bsft.Scheduling.Correlation
Requires Bsft.Correlation and Bsft.Scheduling (both pulled transitively) and no further Bsft
packages. It exists as a package of its own because the scheduler must not drag the ASP.NET Core
request pipeline into a background component: without this bridge the scheduler runs exactly as before
and runs simply carry no correlation id.
Register
services.AddBsftCorrelation();
services.AddBsftScheduling();
services.AddBsftSchedulingCorrelation();
Nothing else is required, and the order does not matter: the core registers its ambient-only default
with TryAdd while this registers the richer accessor with a plain Add, so the bridge wins either
way.
Configure
| Option | Default | Effect |
|---|---|---|
| — | — | — |
None. The package declares no options type and no configuration section; what it registers is a single scoped service. Validation: none.
Extend
None. The package supplies one implementation of the core's IJobCorrelationAccessor seam,
CorrelationContextJobAccessor, which reads ICorrelationContext and lets the ambient id of an
executing job win over the scope's own — without that precedence a chain of jobs, one enqueuing the
next, would start a new correlation on every hop, because each run gets a fresh service scope whose
CorrelationContext mints a new id. A host that wants different behaviour registers its own
IJobCorrelationAccessor and leaves this package out.
Documentation
Topic page: docs/scheduling.md. Conventions: docs/package-conventions.md.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. 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
- Bsft.Correlation (>= 2.2.0)
- Bsft.Scheduling (>= 2.2.0)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.12)
-
net8.0
- Bsft.Correlation (>= 2.2.0)
- Bsft.Scheduling (>= 2.2.0)
- Microsoft.Extensions.DependencyInjection.Abstractions (>= 9.0.19)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.