What is the correct way to swap out MSMQ transport layer to leverage another transport technology under the hood from within the NServiceBus 2.0 API?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What is the correct way to swap out MSMQ transport layer to leverage another transport technology under the hood from within the NServiceBus 2.0 API?
Andreas Ohlund (@andreasohlund) answered my question on twitter with the following:
“You should go for the NServiceBus trunk and implement IMessageQueue (see the Azure queue impl for reference)”
NServiceBus trunk (CodeBetter TeamCity)
Blog post by Andreas Ohlund on NServiceBus Azure transport layer implementation.