Workarounds for resolving the two most common issues when upgrading to version 1.3 of the Windows Azure SDK.
Similar Posts
Mark your calendars! Windows Azure OSS Summit in Paris, France; December 4th, 2012
One of the biggest myths about Windows Azure is that it was created with only .NET developers in mind. The reality is that my team has helped multiple companies around the world implement cloud solutions using a variety of programming languages, including Java, PHP, Node.js and Python, among others. Also, it’s not difficult to find…
Cloud Computing Security Considerations document
High-level discussion of the fundamental challenges and benefits of cloud computing security. Click here to open link…
Gaining Performance Insight into SQL Azure
Since the SQL Profiler is not currently supported for SQL Azure, this article lists a few alternatives on how to measure query performance… Click here to open link…
New FabrikamShipping SaaS Release for Windows Azure SDK 1.3
The Fabrikam Shipping website has been updated to version 1.3 of the Windows Azure SDK. This sample project shows how to create different subscription models using a SaaS approach and different Azure components. Source code is available. Enjoy! Click here to open link…
Windows Azure Domain Name System Improvements
When you publish an application to Windows Azure, it gets its own subdomain in cloudapp.net. In order to make name resolution even faster (particularly outside the USA), the Domain Name System (DNS) used by Azure is moving to a new globally distributed infrastructure. As the article mentions, there is no customer action required. http://blogs.msdn.com/b/windowsazure/archive/2010/09/24/windows-azure-domain-name-system-improvements.aspx
Microsoft JDBC Driver 3.0 for SQL Server and SQL Azure
The latest version of the Microsoft JDBC Driver (3.0) now supports SQL Azure. Click here to open link…