In order to deploy the default ASP.Net MVC 3 web role that comes with version 1.4 (and later) of the Windows Azure SDK, it is necessary to make some changes linked to the SQL connection strings, which point by default to the local SQLEXPRESS instance. This article from Wade Wegner explains how to make them work once deployed to the cloud.
Similar Posts
Announcing Improved In-place Updates for Windows Azure
Two days ago, significant changes and enhancements to the In-place update process were announced for the Windows Azure platform. It is now possible to apply multiple changes to virtual instances without having to redploy the whole solution, including the following: change the VM size, increase the local storage, add or remove roles, or change the…
Microsoft’s Ballmer to Invest Billions in Cloud Data Centers – BusinessWeek
…and working every day on making easier for developers to deploy apps to the cloud. Click here to open link…
Programmatically Changing the AppPool Identity in a Windows Azure Web Role
Excellent blog entry from Wade Wegner, explaining how to change settings for the IIS AppPool associated to a web role in Azure. Click here to open link…
Projecting your Active Directory Identity to the Azure Cloud
How to integrate Active Directory with Azure applications using the Access Control Service (ACS) Click here to open link…
Gartner: Will Microsoft and VMware Dominate the Cloud Landscape?
Current landscape for cloud computing offerings in the market… very interesting. Click here to open link…
Ensuring High Availability of Web Applications in Windows Azure
Deploying more than one instance of your web-facing role enforces the Windows Azure Compute Service Level Agreement (SLA). See the full blog entry from the Azure team… Click here to open link…