Once you begin releasing code out of development, you will need a way to manage configuration changes. When we develop a system, we generally run all the endpoints and have all our message queues on our local machine. When we deploy to new environments, we will need to deploy endpoints to multiple machines and make changes to our configuration.

Our first option is to modify the actual configuration file. As an NServiceBus solution can begin to comprise many different endpoints, I urge you not to try to do this manually.

Visual Studio 2010 introduced a simple method to transform a Web.config file when publishing a website, called XML Document Transform. Unfortunately, this process only supported Web.config files, which was a major oversight, leaving App.config files out in the cold. Luckily, time has passed and tooling has gotten better, so you don't need to let this limitation slow you down these days.

One fairly low-tech solution is the SlowCheetah plugin for Visual...