Rebus .NET Service Bus

For manual control, you can instantiate the RebusBus class directly by providing the necessary dependencies. You must call .Start(int workerThreads) to begin processing and ensure you call .Dispose() when the application exits to clean up resources.

var bus = new RebusBus(...);
bus.Start(1); //< 1 worker thread

// use the bus for the duration of the application lifetime

// remember to dispose the bus when your application exits
bus.Dispose();

The recommended way to set up Rebus is using the Configure.With(...) fluent API. You can use the built-in BuiltinHandlerActivator or integrate your own IoC container using an adapter. Once configured, Rebus registers the IBus instance (typically as a singleton) and uses the container to resolve message handlers.

var someContainerAdapter = new BuiltinHandlerActivator();

Configure.With(someContainerAdapter)
    .Logging(l => l.Serilog())
    .Transport(t => t.UseMsmq("myInputQueue"))
    .Routing(r => r.TypeBased().MapAssemblyOf<SomeMessageType>("anotherInputQueue"))
    .Start();

// have IBus injected in application services for the duration of the application lifetime    

// let the container dispose the bus when your application exits
myFavoriteIocContainer.Dispose();

When using type-based routing, you can restrict the mapping to a specific namespace instead of an entire assembly. This is useful if the assembly contains shared code that should not be routed through a specific queue.

Configure.With(someContainerAdapter)
    .(...)
    .Routing(r => r.TypeBased().MapAssemblyNamespaceOf<SomeMessageType>("namespaceInputQueue"))
    .(...);

// have IBus injected in application services for the duration of the application lifetime    

// let the container dispose the bus when your application exits
myFavoriteIocContainer.Dispose();