Azure-docs: Mixing Microsoft.Azure.ServiceBus and WindowsAzure.ServiceBus client libraries

[inech]

There are two different .NET client libraries to work with Azure Service Bus:

• Microsoft.Azure.ServiceBus (newer, .net standard)
• WindowsAzure.ServiceBus (older, only .net framework)

This article mixes references to both of them and doesn't state explicitly that there are actually two different libraries so it's really hard to follow.

For example here:
> Service Bus client objects, such as _QueueClient_ or _MessageSender_, are created through a _MessagingFactory_ object.
_QueueClient_ and _MessageSender_ are from Microsoft.Azure.ServiceBus but _MessagingFactory_ is from WindowsAzure.ServiceBus which really doesn't make sense.

Also, the code examples are provided only for WindowsAzure.ServiceBus.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: f7eb26ad-3f91-13f4-5827-9dd398412f9d
• Version Independent ID: 1e3dc2ac-1d5e-3da1-7d51-91d36bda14f2
• Content: Best practices for improving performance using Azure Service Bus
• Content Source: articles/service-bus-messaging/service-bus-performance-improvements.md
• Service: service-bus-messaging
• GitHub Login: @axisc
• Microsoft Alias: aschhab

[KetanChawda-MSFT]

@inech Thank you for providing feedback. We will review this and provide an update as appropriate.

[xieb0001]

This documentation contains good information, but with sample code impossible to follow, thus it's very useless. Please update the library usage. I'm struggling to figure out how to make client-side batching with the Microsoft.Azure.ServiceBus library.

[my-name-is]

I agree with @inech. Particularly with the QueueClient and MessagingFactory. We're advised to use a factory but there isn't a factory class for the QueueClient from the "new" Microsoft.Azure.ServiceBus namespace. (Not that I can find). If we're to use a different pattern for keeping connections alive when using the components from the new namespace then please give full examples.

[bojanz27]

Very disappointed that MS still has not consolidated the article to exclusively use Microsoft.Azure.ServiceBus namespace.

[heymega]

I'm in a similar situation to @my-name-is .

I'd like to know the intended lifetimescope of the QueueClient and TopicClient.

[ericsampson]

This documentation is confusing as heck, with its mix of SDKs. It really needs to be rewritten to only talk about Microsoft.Azure.ServiceBus

[codyconfer]

I am still confused by the conflicting information. Can we at least get a reply to this thread on how to using a client factory with the new library? Or is one not needed?

[heymega]

Check out Sean Feldmans answer here...

https://stackoverflow.com/questions/51500645/should-azure-servicebusconnection-be-singleton

Following this advice, I share the connection object as a singleton but use a transient scope for the topic and subscription client.

[jigneshjdesai]

Will this document ever be updated with the correct information? It is misleading.

[IEvangelist]

Hi @inech,

I hope all is well, we've made changes to the doc to address your expressed concern. Please have a look again at the article and let me know if these are satisfactory enough to close this issue.

Merged here, updates to the doc are live here.

[inech]

Hi @IEvangelist,

thank you! Now the documentation is much more clear.