Release Notes for the Service Bus April 2014 Release
Updated: April 3, 2014
|The Windows Azure Service Bus components are now included with the Microsoft Azure SDK. To install, visit the SDK download page.|
These release notes will be updated periodically.
For information about Windows Azure Service Bus pricing, see the Service Bus Pricing FAQ topic.
For a list of new features introduced in the Service Bus April 2014 release, see What's New in the Azure SDK 2.3 Release (April 2014).
Before running Service Bus applications, you must create one or more service namespaces. To create and manage your service namespaces, log on to the Azure Management portal, and click Service Bus. For more information, see How To: Create or Modify a Service Bus Service Namespace.
|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:
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,
Issuer Name: You can use owner, which is an issuer that is created by default for you.
Issuer Key/Secret: You can use the Default Issuer Key listed on the Service Namespace management page on the portal.
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 (v22.214.171.124, v126.96.36.199, and v1.8.00.
The Service Bus assemblies are not installed in the .NET global assembly cache (GAC) by default. The default locations for these assemblies are:
For information about quotas for Service Bus, see Azure Service Bus Quotas.