Just a day before King Willem-Alexander was sworn in in The Netherlands, Microsoft released version 2.0 of the Windows Azure SDK for .NET.
Scott Guthrie described this release as a major refresh with really great new features and enhancements.
These new capabilities include:
- Web Sites: Visual Studio Tooling updates for Publishing, Management, and for Diagnostics
- Cloud Services: Support for new high memory VM sizes, Faster Cloud Service publishing & Visual Studio Tooling for configuring and viewing diagnostics data
- Storage: Storage Client 2.0 is now included in new projects & Visual Studio Server Explorer now supports working with Storage Tables
- Service Bus: Updated client library with message pump programming model support, support for browsing messages, and auto-deleting idle messaging entities
- PowerShell Automation: Updated support for PowerShell 3.0, and lots of new PowerShell commands for automating Web Sites, Cloud Services, VMs and more.
Installation through the Web Platform Installer will install both the VS tools and the SDK, you can download the SDK from the Windows Azure downloads page.
Service Bus Updates
This new version of the SDK also highlights some new Service Bus features. I highlight the Service Bus features just because the Service Bus plays an important role when building hybrid solutions and when using the Service Bus for Integration purposes. There is this one new feature which deserves to be highlighted, Message Pump Programming Model.
The following text is from Scott Gu’s blog;
The Message Pump programming semantics are similar to an event-driven, or “push” based processing model and provides an alternative to the receive loop which we support today. This approach supports concurrent message processing, and enables processing messages at variable rates.
Additional Points of Interest
Here are some other items you need to be aware of, especially if you have been working with Azure for a while.
- WindowsAzure.Diagnostics.dll no longer depends on WindowsAzure.StorageClient.dll. You will now be able to import and use the WindowsAzure.Storage 2.0 NuGet package in your application without introducing conflicts with Diagnostics.
- Windows Azure SDK 2.0 supports side by side with Windows Azure SDK 1.8 and 1.7 while dropping support for side by side with Windows Azure SDK 1.6. Therefore you will not be able to debug an SDK 1.6 service if SDK 2.0 is installed on the same machine.
- WindowsAzure.ServiceRuntime.dll, WindowsAzure.Configuration.dll and the caching assemblies are now built against the .Net framework 4.0 runtime. Therefore you will have to retarget your framework 3.5 application to 4.0 after migrating to Windows Azure SDK 2.0.