Windows Azure SQL Database Marketplace
Editor's Note: This post comes from Avilay Parekh, Windows Azure Senior Program Manager.
Say you have a Windows Azure Cloud Service built with the June 2012 SDK, using .NET 4.0, and OS family 1 or 2. You want to update this to use .NET 4.5 and consequently OS family 3, which is Windows Server 2012. If you use the normal update path, which is to use the “update” button on the Windows Azure portal, or the “publish” button in Visual Studio, the update will fail with an error saying “Upgrade from OS family 1 to OS family 3 is not allowed”. This is a temporary restriction on the update policy that we are working to remove in an upcoming release. In the meant time there are two workarounds to getting your existing Windows Azure Cloud Service running with .NET 4.5 and OS family 3 –
Both have different pros/cons that are mentioned in the table below. Detailed walkthroughs of both the options are provided in this blog.
Let’s assume that your original Cloud Service using .NET 4.0 and OS family 1 or 2 has been deployed to the Production slot in the cloud. The steps to update it to .NET 4.5 and OS family 3 are as follows –
Manually edit the .cscfg file and change the “OSFamily” attribute of the “ServiceConfiguration” element to read “3”.
Deploy the new application to your staging slot in the cloud.
You can deploy from within Visual Studio or from the Windows Azure Portal. In this blog, I’ll show the steps to deploy through the portal.
Perform a VIP Swap of the production and staging slots
Delete your existing application in the cloud.
If you have any questions regarding this post please comment below or reach out to me on Twitter @Avilay.