title: Mass Transit handles Azure Service Bus messages in secondary deployment slot after swap
body: <p>We have an implementation of Mass Transit using Azure Service Bus.  When deploying the application, we first deploy to a staging deployment slot to warm up the service, then swap the slots to put the staging slot into production.  However, messages continue to be handled on the staging slot after the slot swap.  As a stop gap, we now shut down the staging slot after the swap.  But there is a period of time (~15 minutes) that messages get handled before the slot actually shuts down and we cannot risk the errors that might be generated when the handler logic differs between versions.</p>
  <p>Is this a bug in Mass Transit or is there a way to prevent this?  I'm not sure what implementation details I need to provide as I inherited the application. I can provide code...</p>