There have been several changes to v6 to reduce complexity, along with a few enhancements.
MassTransit requires either .NET Standard 2.0 or .NET Framework 4.6.1 (or later). .NET 4.5.2 is no longer supported.
In previous version, using Automatonymous required an additional package,
MassTransit.Automatonymous. The contents of that package are now
included in the
MassTransit assembly/package, which now depends on
Automatonymous. This was done to reduce the number of extra packages
required for container support (along with state machine registration), as well as improve the saga repository persistence assemblies.
When upgrading to v6, any references to the old
MassTransit.Automatonymous package should be removed.
If you are using a container with MassTransit, and were using one of the old container packages for Automatonymous, those package references
should also be removed. With version 6, only the single container integration package is required (such as
The following packages are available for the supported containers:
- MassTransit.Ninject (no registration support)
- MassTransit.Unity (no registration support)
# Azure Service Bus
The previous (now legacy) MassTransit.AzureServiceBus package, which was only maintained to continue support for .NET 4.5.2, has been deprecated. Going forward, the MassTransit.Azure.ServiceBus.Core package should be used. The package supports both .NET 4.6.1 and .NET Standard 2.0.
The previous log abstraction used by MassTransit has been replaced with
The previous log integration packages for Log4Net, NLog, and Serilog have been deprecated. An
ILoggerFactory instance can be
configured for MassTransit by calling:
This should be done prior to configuring the bus.
As of version 6, MassTransit now uses DiagnosticSource for tracking messaging operations, such as Send, Receive, Publish, Consume, etc. An
created for each operation, and context-relevant tags and baggage are added.
# Receive Endpoint Configuration
When MassTransit underwent a major overhaul, and multiple host support was added, that seemed like a great idea. A single bus talking to more than one broker, doing messaging. Reality &emdot; nobody used it. It added a lot of complexity, that wasn't used.
With version 6, a single bus has a single host. That's it. Simple. And with this change, it is no longer necessary to specify the host when configuring a receive endpoint. Yes, the old methods are there, and a pseudo-host is returned from the
.Host() call which can still be passed, but it is ignored. All the transport-specific configuration methods are still there, without the
So, enjoy the simplicity. Under the covers some other things were also made simple &emdot; but I doubt you'll notice.
To be consistent with the rest of MassTransit, many of the interfaces in Courier has been renamed. For example,
ExecuteActivity<TArguments> is now
IExecuteActivity<TArguments>. The previous interfaces are still supported, but have been marked obsolete.
# Conductor (coming soon)
Hard things are hard. Building distributed applications at scale is a hard thing, and it's hard. In fact, it is really hard.
So hard that it isn't ready yet - but there is enough other stuff to warrant releasing v6 without it.
Conductor wants to make it easier, with less complexity.
# MassTransit Host Service (coming later, but soon)
Previous version of MassTransit provided a generalized service host, built using Topshelf, to get started with your first project. But the world has changed. With ASP.NET Core 3.0, and all the goodness that is the generic host, the developer community has moved to a new place.
The latest version of the host is built entirely from scratch, and takes advantage of:
- Microsoft Dependency Injection
- .NET Core Generic Host
- Microsoft Extensions Logging
- MassTransit's most excellent container registration/discovery extensions
Once it's built, the details will all be... revealed!