Release Notes for the Service Bus April 2013 Release

For a list of new features introduced in the Service Bus April 2013 release, see What's New in the Windows Azure SDK 2.0 Release (April 2013).

Account Requirements

Before running Service Bus applications, you must create one or more service namespaces. To create and manage your service namespaces, log on to the Windows Azure Management portal, and click Service Bus. For more information, see How to: Create or Modify a Service Bus Service Namespace.

SDK Samples

Note
By default, the Service Bus samples are no longer installed with the SDK. To obtain the samples, visit the Windows Azure SDK samples page. For an aggregated list of Service Bus samples, with links, see Service Bus Samples.

Most SDK samples and applications contain three authentication requirements:

1. Service Namespace: You can use the service namespace you created in your project on the portal. The service namespace is used to construct Service Bus endpoints (for example, sb://<domain>.servicebus.windows.net/Echo/).
   
   
2. Issuer Name: You can use owner, which is an issuer that is created by default for you.
   
   
3. Issuer Key/Secret: You can use the Default Issuer Key listed on the Service Namespace management page on the portal.
   
   

Runtime Requirements

This release of the Service Bus includes an updated Microsoft.ServiceBus.dll that targets the .NET Framework 4.5 and is backward compatible with previous versions of Microsoft.ServiceBus.dll (v1.0.0.0, v1.5.0.0, and v1.8.00.

Note
The Service Bus assemblies are not installed in the .NET global assembly cache (GAC) by default. The default locations for these assemblies are: C:\Program Files\Microsoft SDKs\Windows Azure\.NET SDK\v2.0\ref.

Note

The RelayConfigurationInstaller.exe tool is no longer shipped with the SDK. This tool enabled you to add the Machine.config settings necessary for Service Bus bindings to be supported in the configuration file. The recommended way to add these bindings now is to add a reference to the Service Bus by installing the NuGet package. NuGet adds the correct entries to the configuration file. For more information, see the NuGet gallery.

Because the Windows Azure SDK 2.0 release does not have a corresponding update for Service Bus for Windows Server, these client libraries are incompatible with that on-premises offering. When we release an update to Service Bus for Windows Server, there will be a corresponding release of the next symmetric client libraries for Service Bus. Meanwhile, the current Service Bus client libraries (version 1.8) remain fully supported on Windows Azure Service Bus as well as Service Bus for Windows Server. Also note that you can use the Service Bus client libraries separately from the Windows Azure SDK, or in conjunction with any version of the Windows Azure SDK that you use to deploy cloud applications.

Service Bus is available in Windows Azure as a PaaS service as well as in a private cloud in Service Bus for Windows Server. The reason for providing these offerings is to enable you to develop, host, and manage applications consistently between the cloud service and on-premises hosted environments. You can write applications against a common set of features and run these applications between these environments with changes only to configuration. Because Windows Azure Service Bus is continually evolving with new features and improvements, it is important to decide which features to consume based on the environment targeted.

For information about quotas for the Service Bus, see Windows Azure Service Bus Quotas.