One of the challenges developers will face when developing Windows Azure web applications is: where do I put my settings? In the ServiceConfiguration file or the web.config? There isn’t one correct answer. The challenge of keeping everything in the web.config is that it makes changes and deployment much more difficult. Because the web.config is part of the deployment, any change to the file also requires a redeployment. If you use a build system that targets your dev/stage/QA/prod environments automatically and can provide the correct settings in the web.config for you, this might mitigate the problem. The answer then is to migrate these settings to the ServiceConfiguration file as it requires no changes to our deployment package. In this screencast I’ll show you some strategies for doing that for components that are more difficult to migrate, like the SqlMembershipProvider… Link to original post and download links.
In my first Azure Miniseries post, I showed setting up a new cloud service project and migrating an existing ASP.NET application into Azure. Before I dive into other topics, I figured I’d jump to the end and discuss deployment – getting your Azure application into the cloud. Link to original post with download links.
I’m starting to put together some short form screencasts on Windows Azure related topics. I’ll use my blog to dive into specifics or display code samples/downloads where appropriate – but first up is a quick look at getting a project setup and migrating existing applications into an Azure webrole.