CODEWITHSUNDEEP
sdkazureservicebusazure-sdk-.netazure-sdk
Mark Cooper
Mark Cooper

Reputation: 6894

Which Azure ServiceBus SDK should be used?

At the time of this post there are two Azure Service bus SDKs sitting within sdk/servicebus:

They have both been updated very recently (past week).

This ms doc (written two weeks ago) states;

This quickstart uses the new Azure.Messaging.ServiceBus package. For a quickstart that uses the old Microsoft.Azure.ServiceBus package, see ....

Where as this document (also written two weeks ago) says;

There are two supported Azure Service Bus .NET SDKs. Their APIs are similar, and it can be confusing which one to choose. Refer to the following table to help guide your decision. We suggest using the Microsoft.Azure.ServiceBus SDK as It's more modern, performant, and is cross-platform compatible. Additionally, it supports AMQP over WebSockets and is part of the Azure .NET SDK collection of open-source projects.

This document goes on to mention Microsoft.Azure.ServiceBus as newer and (yet another SDK) WindowsAzure.ServiceBus as older. It does not mention Azure.Messaging.ServiceBus at all.

Does anyone have any advice on which SDK should be used for a new .NET Core 5.0 project?

(I have already reviewed this question which has not helped)

Upvotes: 1

Views: 163

Answers (1)

Sean Feldman
Sean Feldman

Reputation: 26057

For projects that have no dependency on the older packages, use Azure.Messaging.ServiceBus. For everything else, look at the dependencies. For example, Azure Functions cannot use the latest package today. It will likely be addressed in the future just not ATM. I wrote a blog post awhile ago about these 3 packages. May (or may not) help you with your question.

Upvotes: 3

Related Questions