NServiceBus Message Versioning
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
Modernizing Legacy Applications with AI: A Specification-First Approach
Brad Jolicoeur - 01/03/2026
Transform Your Documentation Workflow with AI: A Hands-On GitHub Copilot Workshop