title: Service Bus Local Dev
body: <p>I'm aware a lot of people have asked about Azure Service Bus local development story and I'm familiar that Microsoft don't provide an on premise solution at the moment. I have also familiarised myself with Jimmy Bogart's writings on the matter.</p>
  <p>I have a variation on the repeated question which I think hasn't been answered before. I have a legacy codebase that is using the older service bus API <code>Microsoft.ServiceBus.Messaging.QueueClient</code> which cannot be easily changed. I also am unable to stub the dependency.</p>
  <p>Ideally I'd like to use something like RabbitMQ on-prem for local dev. I was thinking they both can use AMQP v1.0 protocol. Is it possible to force the Service Bus client to use RabbitMQ (or similar) as an AMQP endpoint with the <code>Microsoft.ServiceBus.Messaging.QueueClient</code> class just with changing the connection string - as a replacement for the ASB dependency? (all I need to support is deferal of messages)</p>
  <p>Appreciate this use case is a little bizarre, but would appreciate any help/thoughts.</p>
  <p>Thanks,
  Chris.</p>