Vulthil.SharedKernel.Outbox
1.2.0
dotnet add package Vulthil.SharedKernel.Outbox --version 1.2.0
NuGet\Install-Package Vulthil.SharedKernel.Outbox -Version 1.2.0
<PackageReference Include="Vulthil.SharedKernel.Outbox" Version="1.2.0" />
<PackageVersion Include="Vulthil.SharedKernel.Outbox" Version="1.2.0" />
<PackageReference Include="Vulthil.SharedKernel.Outbox" />
paket add Vulthil.SharedKernel.Outbox --version 1.2.0
#r "nuget: Vulthil.SharedKernel.Outbox, 1.2.0"
#:package Vulthil.SharedKernel.Outbox@1.2.0
#addin nuget:?package=Vulthil.SharedKernel.Outbox&version=1.2.0
#tool nuget:?package=Vulthil.SharedKernel.Outbox&version=1.2.0
Vulthil.SharedKernel.Outbox
The transactional outbox engine for Vulthil.SharedKernel: the message-capture model (OutboxMessage), the
relay processor and background service, pluggable dispatchers (IOutboxDispatcher), the commit-time relay signal,
and the persistence-agnostic IOutboxStore seam.
It is intentionally persistence-light — free of any EF Core dependency — so a messaging bridge (such as
Vulthil.Messaging.Outbox) can depend on the engine alone. The EF Core implementation lives in
Vulthil.SharedKernel.Outbox.EntityFrameworkCore, and the full infrastructure package
(Vulthil.SharedKernel.Infrastructure) references the engine and adds the DbContext base, the
database-infrastructure configurator, and the DI wiring (EnableOutboxProcessing).
See the Outbox Pattern article on the documentation site for the design and usage.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net9.0 is compatible. 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
- Microsoft.Extensions.Hosting.Abstractions (>= 10.0.10)
- Microsoft.Extensions.Options.ConfigurationExtensions (>= 10.0.10)
- OpenTelemetry.Api (>= 1.17.0)
- OpenTelemetry.Extensions.Hosting (>= 1.17.0)
- Vulthil.Extensions.Hosting (>= 1.2.0)
- Vulthil.SharedKernel.Application (>= 1.2.0)
-
net9.0
- Microsoft.Extensions.Hosting.Abstractions (>= 10.0.10)
- Microsoft.Extensions.Options.ConfigurationExtensions (>= 10.0.10)
- OpenTelemetry.Api (>= 1.17.0)
- OpenTelemetry.Extensions.Hosting (>= 1.17.0)
- Vulthil.Extensions.Hosting (>= 1.2.0)
- Vulthil.SharedKernel.Application (>= 1.2.0)
NuGet packages (3)
Showing the top 3 NuGet packages that depend on Vulthil.SharedKernel.Outbox:
| Package | Downloads |
|---|---|
|
Vulthil.SharedKernel.Outbox.EntityFrameworkCore
Entity Framework Core implementation of the Vulthil.SharedKernel.Outbox engine — the IOutboxStore (capture + the transactional relay batch unit), the ISaveOutboxMessages context marker, the domain-event capture interceptor, and the OutboxMessage mapping. Referenced by the relational/provider store packages and the infrastructure host; keeps the outbox engine itself free of any EF Core dependency. |
|
|
Vulthil.SharedKernel.Infrastructure
Infrastructure helpers for persistence, transactions, outbox, and EF Core integration. |
|
|
Vulthil.Messaging.Outbox
Transactional bus-publish outbox for Vulthil.Messaging. A publish/send filter captures messages published inside a database transaction into the shared outbox table; the outbox relay sends them to the broker after the transaction commits, with a stable message id, eliminating the dual-write problem. |
GitHub repositories
This package is not used by any popular GitHub repositories.