NServiceBus Message Versioning

NServiceBus Message Versioning
by Brad Jolicoeur
10/02/2018

As a software engineers we all know the requirements will change over time. At some point you will need to become comfortable with versioning your NServiceBus messages to adapt to those changing requirements. When you start thinking about the nuances of deploying endpoints that need to handle messages of different versions in flight or in an error queue waiting for retries it can be overwhelming at first. Luckily, there is a straight forward and relatively painless way to make changes to your contracts that will enable your endpoints to process old and new versions in parallel.

In this short video I walk through a versioning scenario where I implement a new version of an event using inheritance.

You can find the source code for this project on GitHub: NSB.Example.MessageVersioning

You May Also Like


Profiling .NET 10 Applications: The 2026 Guide to Performance

dotnet-profiler.png
Brad Jolicoeur - 02/14/2026
Read

The Trap of Database Triggers in Event-Driven Architecture

trigger-mouse-trap.png
Brad Jolicoeur - 02/13/2026
Read

The FIFO Fallacy: Why Ordered Queues are Killing Your Scalability

fifo-queues.png
Brad Jolicoeur - 01/31/2026
Read