Brainograph.Messaging.Wolverine 2.1.1

.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher.
The owner has unlisted this package. This could mean that the package is deprecated, has security vulnerabilities or shouldn't be used anymore. 
dotnet add package Brainograph.Messaging.Wolverine --version 2.1.1
                    


                    

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


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Brainograph.Messaging.Wolverine" />
                    


                            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 Brainograph.Messaging.Wolverine --version 2.1.1
                    


                    

                
#r "nuget: Brainograph.Messaging.Wolverine, 2.1.1"
#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 Brainograph.Messaging.Wolverine@2.1.1
#: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=Brainograph.Messaging.Wolverine&version=2.1.1
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Brainograph.Messaging.Wolverine&version=2.1.1
                    


                            Install as a Cake Tool

WolverineFx (multi-transport: PostgreSQL, RabbitMQ, or Azure Service Bus) provider for the Brainograph.Messaging seam. References only Brainograph.Messaging.Abstractions + WolverineFx (+ WolverineFx.Postgresql/WolverineFx.RabbitMQ/WolverineFx.AzureServiceBus for the transport-specific strategies).

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

2.1.1 — fixes a benign teardown race in the soft-boot producer hosted service (introduced with the soft-boot change in 2.0.1): under WebApplicationFactory disposal the host could Dispose() the hosted service — disposing its stopping CancellationTokenSource — before/without an orderly StopAsync, so StopAsync's `_stopping.CancelAsync()` threw ObjectDisposedException. StopAsync now guards only that CTS interaction so the stop path is idempotent and dispose-safe in any interleaving; real process shutdown was never affected, but downstream test factories no longer need a scoped catch. No API change. 2.1.0 — adds an OPT-IN durable outbox for the brokered transports (RabbitMq/ASB), the fix for the 2.0.x sender-side at-least-once gap: set `Messaging:Wolverine:DurableOutbox:Enabled=true` (+ `:ConnectionString`, typically the service's own app DB, and optional `:Schema`, default `messaging`). It adds a Postgres message store, and the producer's durable send path enlists a fresh MessageContext in a store transaction and publishes via BroadcastToTopicAsync (a ROUTED send — a bare EndpointFor(uri).SendAsync bypasses the outbox), so the outgoing envelope is PERSISTED to wolverine_outgoing_envelopes on commit and forwarded by the durability agent — a broker OUTAGE no longer loses the produce (proven by DurableOutboxBrokerOutageTests: produce during a stop_app outage lands in the store and is delivered exactly-once after start_app). Off by default → 2.0.x behaviour (broker-native durability, documented gap) is unchanged for anyone who does not set it. 2.0.0 — transport config-selectable via `Messaging:Wolverine:Transport`; RabbitMQ + ASB transports (native fan-out); same consume-side contract on all three. See MESSAGING-TRANSPORTS.md §4.4.