Stratara.Outbox.AzureServiceBus 4.4.4

Prefix Reserved
.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package Stratara.Outbox.AzureServiceBus --version 4.4.4
                    


                    

                
NuGet\Install-Package Stratara.Outbox.AzureServiceBus -Version 4.4.4
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.Outbox.AzureServiceBus" Version="4.4.4" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="Stratara.Outbox.AzureServiceBus" Version="4.4.4" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Stratara.Outbox.AzureServiceBus" />
                    


                            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.Outbox.AzureServiceBus --version 4.4.4
                    


                    

                
#r "nuget: Stratara.Outbox.AzureServiceBus, 4.4.4"
#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.Outbox.AzureServiceBus@4.4.4
#: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.Outbox.AzureServiceBus&version=4.4.4
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Stratara.Outbox.AzureServiceBus&version=4.4.4
                    


                            Install as a Cake Tool

Stratara.Outbox.AzureServiceBus

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

License: MIT.

Azure Service Bus implementation of Stratara.Abstractions.Messaging.IMessageBus. Publishes JSON-serialized messages to topics and exposes a subscription helper that wires up a Service Bus processor with per-message exception classification:

  • success → CompleteMessageAsync
  • ConcurrencyException → AbandonMessageAsync until MessageRetry:MaxConflictRequeues redeliveries (default 100) have not resolved it, then DeadLetterMessageAsync with reason conflict
  • any other exception → AbandonMessageAsync until MessageRetry:MaxDeliveryAttempts deliveries (default 3) have failed, then DeadLetterMessageAsync with reason failure and the exception in the description

The subscription's own MaxDeliveryCount must leave room for the bounds; a subscription created with Service Bus defaults allows 10 deliveries. Where the host can read the subscription, the bus lowers the bounds for it to fit and logs 108_111.

System-level errors (connection drops, auth failures) arrive via ProcessErrorAsync and are logged; the Service Bus client owns the reconnect / retry policy for those.

A subscription that stops closes its processor, which takes no further message and waits for its running handler — as long as the host's shutdown timeout allows while the application stops, twenty seconds otherwise; the host waits for that before it counts as stopped. A handler that gives up because the subscription stops has its message abandoned rather than dead-lettered by the framework; the broker counts that delivery like any other. A handler's outcome is settled whatever the subscription's own cancellation says, and a handler that failed because its save committed but could not publish has its message completed, not delivered again.

Install

dotnet add package Stratara.Outbox.AzureServiceBus

Register the bus in your DI composition — one call wires the ServiceBusClient, the envelope options and the IMessageBus implementation:

// Connection string:
builder.Services.AddAzureServiceBus(builder.Configuration.GetConnectionString("ServiceBus")!);

// Or, preferred in Azure — managed identity, no secret in configuration:
builder.Services.AddAzureServiceBusWithManagedIdentity("my-namespace.servicebus.windows.net");

The AzureServiceBusBus implementation is internal; register it through these extensions rather than by naming the type.

The explicitly-chosen transport wins. AddAzureServiceBus replaces the IMessageBus registration, so it takes effect even when the RabbitMQ umbrella (builder.AddMessaging(), which the worker composites call) already claimed the slot. Still use one transport per host — calling both is a configuration smell — but an explicit AddAzureServiceBus will no longer be a silent no-op behind a composite.

Notes

Pre-3.0 this implementation lived inside Stratara.Outbox.RabbitMQ. As of 3.0 the two transports are separate packages so a consumer who only wants RabbitMQ does not drag the Azure Service Bus SDK into the dependency tree (and vice versa).

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.4.6 0 10/22/2026
4.4.5 85 10/14/2026
4.4.4 89 10/10/2026
4.4.3 95 10/10/2026
4.4.2 100 10/2/2026
4.4.1 95 9/29/2026
4.4.0 95 9/27/2026
4.3.1 104 9/25/2026
4.3.0 100 9/23/2026
4.2.0 112 9/18/2026
4.1.1 106 9/16/2026
4.1.0 96 9/16/2026
4.0.4 112 9/14/2026
4.0.3 110 9/3/2026
4.0.2 115 9/3/2026
4.0.1 104 9/2/2026
4.0.0 108 8/31/2026
4.0.0-preview.1 77 8/31/2026
3.4.0 111 8/28/2026
3.3.0 109 8/25/2026
Loading failed

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.