Web Apps

2 Alternate Configurations for Windows Azure Deployment

April 18, 2014

I’ve become a big fan of Windows Azure as a web application platform. One my favorite features is that you can use GitHub or BitBucket as a repository source, and Azure will download, recompile, and deploy your solution whenever you commit changes to it.

By default, Azure deployments will grab the first web application project in your solution and use the release configuration contained in it for deployment. This may not be how your solution is configured or how you want to deploy the project. Fortunately, there are a couple of settings that allow you to change this.

To make these changes, log in to your Azure control panel, select your web site, and then select the “Configure” option. From there, scroll down to the “App Settings” section and configure accordingly.

Use a Different Project

For one project, we kept a “webui” solution that was a static HTML site to demonstrate UI/UX for the customer. This project was not the first project in the solution. In order to have Azure deploy this project, I added the following setting:

Key: Project
Value: webui/webui.csproj

This told Azure to pull the code from that particular folder and use it for deployment. Since the .csproj file has all of the required files listed in it, it was able to compile and deploy without a problem. You can do the same by replacing the folder/project file name with your appropriate values.

Use the Debug Deployment Configuration

For this same project, I had a test database and URL setup and kept the appropriate web.config tranform values in my web.debug.config file. In order to have Azure compile with these values, I added  the following setting:

Value: -p:Configuration=Debug

If you’ve generated other web.config transform files, you can replace the “Debug” value with the appropriate transformation name.

That’s all there is to it. Save the settings, go back to your deployments section and click either the “Sync” or “Redeploy” buttons and your changes will show up momentarily.

By enabling these settings, there was no need to make any special file changes or to keep test values in a release configuration. We let the deployment tool work as it should. I hope this helps you with your Azure deployments!

Enhanced by Zemanta

Sean Patterson

Software Development Director

Sean Patterson is a Software Development Director at Fresh Consulting. By day he develops applications at Fresh with the motto "If you can dream it, I can build it." By night he's a java overlord (of the coffee persuasion), aspiring running junkie, spider killer for his wife, and silly daddy to his twin daughters.

You might also like...



Autocomplete: Varieties, Benefits & UX Best Practices

For just about everything besides scenic drives, people prefer shortcuts. And if a shortcut not only gets you there quicker but also takes you to a better destination, now that’s something! This is what autocomplete does. By giving users the option of completing words and forms based on what they’ve typed before, it shortcuts their … Continued



10 Factors for Choosing a CMS

There are dozens of Content Management System (CMS) platforms available to to help you manage the content, marketing, and SEO on your website. But with all the good options out there, how do you know how to choose the right CMS? Consider the following 10 factors when choosing your CMS. #1 Price Some CMS licenses start … Continued



How Will the Oracle Java Licensing Changes Affect You?

Earlier this year, Oracle announced that beginning January 1, 2019, it will no longer provide support and updates to Java SE 8. Instead, the support and updates that have been included as part of the Java license will now be available only through a separate subscription support service. As we are now well into the … Continued