Stratara.Outbox.AzureServiceBus 4.4.9

Prefix Reserved
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.9
                    
NuGet\Install-Package Stratara.Outbox.AzureServiceBus -Version 4.4.9
                    
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.9" />
                    
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.9" />
                    
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.9
                    
#r "nuget: Stratara.Outbox.AzureServiceBus, 4.4.9"
                    
#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.9
                    
#: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.9
                    
Install as a Cake Addin
#tool nuget:?package=Stratara.Outbox.AzureServiceBus&version=4.4.9
                    
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.8.0 103 11/6/2026
4.7.1 97 11/5/2026
4.7.0 106 10/30/2026
4.6.1 105 10/29/2026
4.6.0 102 10/28/2026
4.5.0 107 10/28/2026
4.4.10 103 10/26/2026
4.4.9 98 10/26/2026
4.4.8 100 10/24/2026
4.4.7 102 10/23/2026
4.4.6 97 10/22/2026
4.4.5 108 10/14/2026
4.4.4 107 10/10/2026
4.4.3 111 10/10/2026
4.4.2 113 10/2/2026
4.4.1 107 9/29/2026
4.4.0 109 9/27/2026
4.3.1 116 9/25/2026
4.3.0 113 9/23/2026
4.2.0 123 9/18/2026
Loading failed

A fix for hosts on the Orleans execution model. A host that removed or renamed a projection no longer has that
projection's store readers come back on every start and fail each entry; they retire once, as a saga's readers do. A
retired store reader now logs its retirement once instead of three times, and leaves no reminder error behind. No
API change, no schema change and no migration.

### Fixed

- **A reader of a removed projection retires.** On the Orleans execution model, a host that removed or renamed a
 projection kept the keep-alive reminders of its store readers. On every start of the silo they brought the readers
 back, and each one read the next entry of its partition, failed it because no projection of its name was
 registered, and tried again on the next tick, without end — a warning per partition and entry. Such a reader now
 retires the first time it is brought back, as a saga's reader already did: it unregisters its keep-alive, logs
 `117_136` `UnregisteredProjectionReaderRetired` (Information) once, reads nothing and deactivates. Its checkpoints
 stay, so a projection registered again resumes where it stopped; *Operate the Orleans execution model* says how to
 delete them. In a rolling deployment that adds a projection, a reader that lands on a silo of the earlier version
 refuses a rebuild's or a replay's pause, which then fails naming it, and a wait counts its partition as behind.
- **A retired store reader logs its retirement once.** A reader that retired as it was activated — of a partition
 beyond a lowered partition count, or of a saga the silo no longer registers — deactivated before it answered the
 call that activated it. Orleans forwarded that call to a new activation, which retired again, so the retirement was
 logged three times per reader and the keep-alive tick ended in `Could not deliver reminder tick` at Error. The
 reader now answers the call first and deactivates after it.