azure-service-bus-dotnet | ️ .NET Standard client library for Azure Service Bus | Pub Sub library

 by   Azure C# Version: v3.4.0 License: Non-SPDX

kandi X-RAY | azure-service-bus-dotnet Summary

kandi X-RAY | azure-service-bus-dotnet Summary

azure-service-bus-dotnet is a C# library typically used in Messaging, Pub Sub applications. azure-service-bus-dotnet has no bugs, it has no vulnerabilities and it has low support. However azure-service-bus-dotnet has a Non-SPDX License. You can download it from GitHub.

Azure Service Bus allows you to build applications that take advantage of asynchronous messaging patterns using a highly-reliable service to broker messages between producers and consumers. Azure Service Bus provides flexible, brokered messaging between client and server, along with structured first-in, first-out (FIFO) messaging, and publish/subscribe capabilities with complex routing.

            kandi-support Support

              azure-service-bus-dotnet has a low active ecosystem.
              It has 238 star(s) with 120 fork(s). There are 48 watchers for this library.
              It had no major release in the last 12 months.
              There are 66 open issues and 317 have been closed. On average issues are closed in 83 days. There are 4 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of azure-service-bus-dotnet is v3.4.0

            kandi-Quality Quality

              azure-service-bus-dotnet has 0 bugs and 0 code smells.

            kandi-Security Security

              azure-service-bus-dotnet has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              azure-service-bus-dotnet code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              azure-service-bus-dotnet has a Non-SPDX License.
              Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

            kandi-Reuse Reuse

              azure-service-bus-dotnet releases are available to install and integrate.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of azure-service-bus-dotnet
            Get all kandi verified functions for this library.

            azure-service-bus-dotnet Key Features

            No Key Features are available at this moment for azure-service-bus-dotnet.

            azure-service-bus-dotnet Examples and Code Snippets

            No Code Snippets are available at this moment for azure-service-bus-dotnet.

            Community Discussions


            How do I use MSI to access a Service Bus from a VMSS in Azure
            Asked 2019-Jun-13 at 07:40

            My console application is running on a VM in an Azure Scale Set but is not able to connect to an Azure Service Bus using the VMSS Managed Service Identity.

            An exception is thrown when it attempts to acquire an access token via TokenProvider.CreateManagedServiceIdentityTokenProvider().

            1. The Identity (System Assigned) is enabled on the Virtual Machine Scale Set (VMSS ).
            2. The VMSS Identity is assigned the Role Azure Service Bus Data Owner on the Service Bus Namespace

            Is there a step or requirement that I am missing?

            Sample code



            Answered 2019-Jun-13 at 05:17

            As per the exception message, it looks like Managed identity is not enabled on the VMSS. How did you verify that it is enabled?

            Also, can you please specify which Service Bus NuGet package are you using, and what version?



            Send a message with a new library (Microsoft.Azure.ServiceBus) that is read by an old library (Microsoft.ServiceBus.Messaging) with BodyType - String
            Asked 2019-May-08 at 20:56

            I have a client written for some time ago that uses the old library and does call GetBody() to read the body when receiving messages.

            Now I have the new client Microsoft.Azure.ServiceBus (sends messages) that as far as I understand always uses Stream.

            So the old client just crashes as it expects string body type. I have found a lot of information on the opposite scenario (new reader, old writer), but cannot figure out how to make the new client send the data in required format.

            Related links:

            1. A stackoverflow answer
            2. Interop extension to do the opposite (read an old message in the new client)


            Answered 2019-May-08 at 20:56

            The scenario is described here. You will need to serialize the message following this approach:



            Azure Service Bus keeps throwing MessageLockLostExceptions
            Asked 2018-Dec-15 at 19:51

            I keep getting MessageLockLostExceptions when processing messages.

            Now I want to simulate a slightly longer running message processing task (but still well within LockDuration) by adding Task.Delay(10_000). But then I get a MessageLockLostException for exactly every 4th message.

            This happens even if I set MaxAutoRenewDuration = TimeSpan.FromDays(30) and PrefetchCount = 0.

            This is the message processing method, which I changed slightly to print out the remaining lock duration:



            Answered 2018-Dec-13 at 04:35

            You need to Complete the message before the Lock Token gets expired. Once the Lock Token is expired, you will receive MessageLockLostException during the complete operation.

            I can see that you are delaying the thread execution by 10 seconds for each message. But the messages seems to be fetched at the same point of time, that's why the remaining lock duration keeps reducing for each message.

            For the fourth message, the Remaining lock duration is 00:00:00.1776760. So, after 177 milliseconds, the lock will expire. You are delaying the thread by 10 seconds in the next line. So, the lock would expire and you are getting MessageLockLostException. To avoid this exception, remove the Delay



            Service Bus NET Core client (NET Standard client). Unable to connect to on prem servicebus instance
            Asked 2018-Mar-01 at 22:19

            I downloaded the code from here:

            and tried try to run the tests but am getting this: Message: System.TypeInitializationException : The type initializer for 'Microsoft.Azure.ServiceBus.UnitTests.TestUtility' threw an exception. ---- System.ArgumentException : Illegal connection string parameter name 'StsEndpoint' Parameter name: connectionString

            I'm using on premise service bus version. Is this not supposed to be supported? This is the connection string I use:


            This same connection string works fine with other tools e.g. Service Bus Explorer

            If I remove couple of the "unsupported" parameters and simplify my conn string to this: Endpoint=sb://;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=bKnerepD9LBGHIVAM4nXJTw5kAAP5updfQYhH2gFG/o=

            I get this error: Message: Microsoft.Azure.ServiceBus.MessagingEntityNotFoundException : None of the server sasl-mechanisms ([PLAIN,EXTERNAL]) are supported by the client (MSSBCBS).

            I've opened an issue on the project's site for this as well




            Answered 2018-Mar-01 at 22:19

            As answered in the issue you opened, new .Net Core client (Microsoft.Azure.ServiceBus) only supports SAS authentication, which is not available for on-premises Service Bus.



            Send a message on Azure ServiceBus from .NET Core sender to a .NET 4.6 handler
            Asked 2017-Jul-13 at 00:24

            I want to send a message over Azure Service Bus from a .NET Core console app and receive it with in a .NET 4.6 console app. In .NET Core I'm using Azure's new service bus client for the sender which is not yet intended for production (according to their readme).


            I can send from .NET Core and receive with .NET Core easily enough using the samples. However when the .NET 4.6 app subscribes to the Topic and receives the same message the .NET 4.6 app throws this exception:



            Answered 2017-Jul-12 at 23:35

            Sounds like an interoperability issue

            The fix was merged into dev branch, but hasn't gone out yet. Scheduled for 0.0.7-preview milestone`. You can track it under the GitHub repo.


            Community Discussions, Code Snippets contain sources that include Stack Exchange Network


            No vulnerabilities reported

            Install azure-service-bus-dotnet

            You can download it from GitHub.


            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
          • HTTPS


          • CLI

            gh repo clone Azure/azure-service-bus-dotnet

          • sshUrl


          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link

            Explore Related Topics

            Consider Popular Pub Sub Libraries


            by greenrobot


            by apache


            by celery


            by apache


            by apache

            Try Top Libraries by Azure


            by AzureTypeScript


            by AzureC#


            by AzurePython


            by AzureJupyter Notebook