NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet · #2437 most downloaded on NuGet
Provides an Autofac container adapter for Rebus
Last release 3 years ago
no release in 18 months
Ships fairly regularly
a new release about every 4 months
Nearly every release is documented
notes for 56 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
14 years old
358 releases · first in 2012
Don't rethrow ResolutionException inside another ResolutionException in case of configuration errors - the stack trace reveals the call stack so nicel
ResolutionException inside another ResolutionException in case of configuration errors - the stack trace reveals the call stack so nicely, there's no need to have 10 layers of exceptions tooIFailed<TMessage> anywhere (because it is most likely an error)Moved defer-recipient header check to the pipeline, giving other pipeline steps a chance to set it
One column per quarter.
Better error behavior when deferring a message from a one-way client without setting the defer-recipient
Added ability to set up fake saga data in SagaFixture
SagaFixtureFakeBusAdded option for Azure Service Bus transport to skip queue creation to make it possible to use a read-only SAS key instead of a connection string with
Updated StructureMap dependency to 4.1.2.386 - thanks [dougkwilson]
TransactionScope support extensionFixed bug in Rebus' protobuf serializer that caused it to be unable to serialize Rebus' control bus messages
Fixed RavenDB subscription and timeout storage
Added correlation sequence number as an auto-flowing header too - can be used to deduce causation
Brough back FakeBus - an implementation of IBus that records everything that happens to it as events which you may query during the assert-phase of yo
FakeBus - an implementation of IBus that records everything that happens to it as events which you may query during the assert-phase of your testsSagaFixture to ease saga testingFixed saga correlation bus introduced in 0.99.37
Fixed subtle unintented behavior so that messages inherited from an initiating type can initiate sagas too
Much improved error message when sending to non-existent queue with Azure Service Bus
Failed<TMessage> to be IFailed<TMessage> (and thus an interface) in order to make it covariantFixed bug that caused the Azure Service Bus transport to not be properly initialized when using the "Basic" tier - thanks [torangel]
Made small improvements to Rebus.Async (added timeout option + added ability to remove abandoned replied when their age exceeds a configurable thresho
Fixed bug where an exception thrown while correlating an incoming message with a saga would not be included as inner exception - thanks [mortenherman]
Fixed logging of the configured region with Amazon SQS transport - thanks [gertjvr]
Added unit of work guards and fixed bug that would result in exceptions when providing no rollback/cleanup action when using the async version
Removed hardcoded region settings in purge operation with SQS transport - thanks [gertjvr]
Fixed Rebus.MongoDb package (nuspec was lying about its MongoDB driver dependency)
* Added Wire serializer
Fixed bug in RavenDB saga persister - thanks [bjomi] and [jsvahn]
Fixed options configuration API to be more consistent and thus less prone to confusion - thanks [xenoputtss]
Fixed bug in in-mem saga storage that would accidentally enforce uniqueness of correlation properties across saga data types
Fixed it so that SQL Server transport does not start the background "expired messages cleanup" task when it is a one-way client
Added RavenDB saga persister - thanks [bjomi]
Small changes to Rebus' TransactionScope enlistment support
TransactionScope enlistment supportFixed bug in Amazon SQS transport that would silently ignore errors when sending messages - thanks [gertjvr]
Fixed Rebus' SimpleInjector container adapter registrations to be able to resolve IMessageContext as part of the container's verification process
IMessageContext as part of the container's verification processFixed bug that would fail saga data auditing when the message could not be correlated with a saga data instance
Added IBus API overloads for Subscribe and Unsubscribe that accept a Type as a parameter - thanks [gertjvr]
IBus API overloads for Subscribe and Unsubscribe that accept a Type as a parameter - thanks [gertjvr]ExpiredMessagesCleanup warning because of locked rows when handling message for a long time with the SQL Server transportrbs2-defer-recipient header to designate the queue to deliver the message to when it returns - allows for doing request/reply with a defer in the middle without losing the return address (which must be transferred manually, though, unless you bus.Advanced.TransportMessage.Defer)ResolveConflictAdded EnlistRebus option to Rebus.TransactionScopes, allowing for easily enlisting an ambient Rebus transaction in an ambient .NET transaction
EnlistRebus option to Rebus.TransactionScopes, allowing for easily enlisting an ambient Rebus transaction in an ambient .NET transactionGeneral handling of receive errors by logging as warning
Added DryIoc container adapter - thanks [dadhi]
Added LightInject container adapter - thanks [puzsol]
Added ability to immediately forward messages on certain exception types (optionally when those exceptions satisfy some predicate)
Fixed nuspec on StructureMap package, made SimpleInjector package dependency version criteria more tolerant, and updated the Unity dependency to v 4
Changed RabbitMQ routing to use two exchanges: one for direct addressing, and one for pub/sub messaging. This way, "clean" RabbitMQ topics can be subs
Fixed it so that delivery will not be retried indefinitely on commit exceptions
Limit length of header values used when using Azure Service Bus transport
Replaced Windsor's assembly-scanning with manual scan
Added no-inlining jit directive to the Windsor package's AutoRegisterHandlersFromThisAssembly method because it looks like handlers are sometimes not
AutoRegisterHandlersFromThisAssembly method because it looks like handlers are sometimes not picked up as they should* Fixed NLog nuget dependency
Added Serilog log event enricher + configuration extension for including Rebus' correlation ID in log events
${rebus-correlation-id} variableInject loggers. Will remove static logging things later.
Added ability to mark saga data as unchanged by calling MarkAsUnchanged() on the saga handler.
MarkAsUnchanged() on the saga handler.Added IMessageContext.AbortDispatch() which aborts dispatch of the current message to any handlers following the one currently being executed.
IMessageContext.AbortDispatch() which aborts dispatch of the current message to any handlers following the one currently being executed.Extended built-in handler activator with Register overloads that allow for registering handler factory functions that accept IMessageContext and (IBus
Register overloads that allow for registering handler factory functions that accept IMessageContext and (IBus, IMessageContext) as argumentsFixed MSMQ remote queue path formatting
Fixed bug that could result in double-resolving handler instances with Ninject, Castle Windsor, and Unity because of a lazy-evaluated IEnumerable
IEnumerableAdded simple 2nd level retries mechanism
Added "per Rebus message" lifestyle to Windsor container configuration extensions
Added one-way client mode for Amazon SQS transport
Added IsNew property to Saga base class allowing saga handlers to easily determine whether the instance is new
IsNew property to Saga base class allowing saga handlers to easily determine whether the instance is newMade disposal of resources more consistent (still not entirely consistent though, depends on importance)
Added transport message routing capability
Set message label on sent MSMQ messages (is shown in MSMQ tools like Rebus Snoop etc.)
Updated SimpleInjector dependency to 3.0.1
Change RabbitMQ transport to allow for using Rabbit's native pub/sub capabilities, thus removing the need for a subscription storage
Moved the explicit routing function to an advanced routing API
Your coding agent can read these notes before it upgrades. Set up the MCP server →