Your opinion matters! Please fill in the InfoQ Survey!

Windows Azure Service Bus Client SDK with Task Based Asynchronous API

| by Anand Narayanaswamy Follow 0 Followers on May 30, 2013. Estimated reading time: 1 minute |

A note to our readers: As per your request we have developed a set of features that allow you to reduce the noise, while not losing sight of anything that is important. Get email and web notifications by choosing the topics you are interested in.

Microsoft recently released Windows Azure Service Bus Client SDK with System.Threading.Tasks.Task based versions of all  asynchronous APIs including the ability to write asynchronous and readable code. The latest release has been compiled against .NET Framework 4 and hence it will work with both Visual Studio 2012 and its previous counterpart.

Scott Seely, Senior SDE, Windows Azure Service Bus team demonstrates the functioning of the SDK by making use of Microsoft.ServiceBus.NamespaceManager and Microsoft.ServiceBus.Messaging.QueueClient in the official MSDN blog post titled - Task Based APIs for Service Bus.

He then attempts to verify whether the queue exists, create the queue if it does not exist and send/receive a message from the queue. Scott demonstrates the code in such a way that the message will be delivered about 5 seconds after it is sent to enable client to perform other activities with the CPU instead of waiting for the message to show up and return.

Windows Azure Service Bus Client SDK has been developed in such a way that all exceptions only throw when the task completes including the ability to hold on to the task and wait for it to complete and can be installed either via the NuGet or using package manager console in Visual Studio.

In addition to the above mentioned features, Windows Azure Service Bus Client SDK also ships with support for message browsing, ability to suspend and resume sending and receiving messages to and from queues and topics by using the Microsoft.ServiceBus.Messaging.EntityStatus enumeration and ability to auto delete idle queue, topic or subscription after an interval specified in AutoDeleteOnIdle property.

The recent release of the SDK introduces an event-driven or push messaging programming model, which is an alternative to a receive loop with support for concurrent message processing including an ability to process messages at variable rates.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you