WindowsAzure.ServiceBus 3.0.1

• • Microsoft.WindowsAzure.ConfigurationManager

Build: 2.0.50398.0
• General: Compiled against .Net 4.5
   - if you have a .Net 4.0 project you should recompile against .Net 4.5 instead since 4.0 project cannot reference 4.5 dll.
• General: Removal of Asynchronous Programming Model (APM) API for all Messaging and EventHub classes.
   - If your application use the old APM API you should switch over to use the Task-based Asynchronous Pattern (TAP) API instead
   - e.g. instead of using QueueClient.BeginSend/EndSend, please use QueueClient.SendAsync.
   - For more information on interop between APM and TAP, please refer to https://msdn.microsoft.com/en-us/library/hh873178(v=vs.110).aspx
   - Note: support for CancellationToken in the TAP model will be implemented in later SDK update.
• General: Removal of Notification Hub API from Microsoft.ServiceBus.dll.
   - To get the NotificationHub functionality please use the Microsoft.Azure.NotificationHubs nuget package instead: https://www.nuget.org/packages/Microsoft.Azure.NotificationHubs/
• General: ServiceBusEnvironment.SystemConnectivity.Mode now support explicit Https mode.
• EventHub/Messaging: AutoDetect will now perform detection in both Sbmp and Amqp transport.
   - Detection happens at the first operation per AppDomain, and the purpose of the detection is to determine if the low level host and port requirement are functional.
   - Once a detection completes the state is not changed unless AppDomain is unloaded or system network state has changed.
   - The perference of mode used is tcp -> https (port 443) -> http (port 80).
• EventHub/Messaging: Amqp transport will always use WebSocket implementation when using Https or Http mode.
• EventHub/Messaging: New Api MessagingFactory.ResetConnection() to support manual internal connection reset.
   - This gives user a more predictable control on when a transport level connection should be recreated.
   - This is only implmented for Amqp transport. Other transports will throw NotSupportedException.
• EventHub: Low level data from the Amqp’s message Annotation section will now show up in EventData.SystemProperty
• EventHub: Remove DataContractSerializer dependency from EventHub by removing EventData.GetBody()
   - User should use EventData.GetBodyStream() or EventData.GetBytes() to get the body stream/bytes, and pass it to the serializer if desired.
• EventHub: Client side support for future link level redirection work.
• EventHub: Connection string now support additional connection param for future link level redirection work: HostName, AmqpSecurityScheme, CredentialType
• Messaging: QueueClient and SubscriptionClient now exposes RenewMessageLock(lockToken) Api.
• Messaging: Optimization on connection/factory instances when creating client using XXXClient.CreateFromConnectionString()
   - Multiple client creation using the same connection string (within the same AppDomain) will now use the same cached MessagingFactory instance.
   - Connection string equality will now be based on key-value pair comparison rather than plain-string comparison. This means the ordering of the key-value pair within the string will not matter anymore.
   - Note: MessagingFactory.CreateFromConnectionString will not be affected and will still create new instances everytime the method is called.