These postings are provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use.
Jonathan RozenblitDeveloper Evangelist
Susan IbachDeveloper Evangelist
A few weeks ago, the Windows Azure SDK v1.5 was released with many enhancements and fixes that further simplifies development, deployment, and management of applications on the Windows Azure platform.
As soon as it was released, I headed over to the SDK download page (Web Platform Installer), downloaded the latest version, and started exploring the new features. Reading through discussions on stackoverflow.com and various groups on LinkedIn (including the Canadian developer community’s own Canadian Developer Connection), it seems that many are still using older versions.
I wanted to let you know that it’s OK to, and that you should, upgrade your projects to v1.5 of the SDK. There’s just one caveat, though, that I’ll get to in a bit.
First, the reasons why upgrading to v1.5 of the SDK is a good thing to do:
And now, the caveat:
The Windows Azure project file (.ccproj) has a different structure in this version from previous versions. When you open a solution that contains a Windows Azure project, any existing .ccproj files are changed to this new structure. This upgraded .ccproj file is incompatible with previous versions of the Windows Azure Tools, which means that if you’re working on a development team, you’ll all need to upgrade to v1.5 in order to continue working on the project.
Windows Azure Platform Training Kit
The Windows Azure Platform Training Kit (Offline, Online) has also been updated to include all of the updates, enhancements, and fixes I mentioned above. It also includes a brand new hands-on lab that explores the new messaging capabilities released with the new version of the Service Bus.
Here’s What You’re Going to Do
Now that you’re aware of the reasons why you should start working with v1.5 of the SDK: