Tip: Automating Dev, QA, Staging, and Production Web.Config Settings

Why not join our community?, there are 15 users online

home
asp.net
view story

DotNetKick.com is an open-source project. Please report any bugs and let us know your great suggestions. Currently running svn revision 637 (rss)

Kick Spy!, Kick Zeitgeist and Kick Widgets

17
kicks

kick it

Tip: Automating Dev, QA, Staging, and Production Web.Config Settings

published 1 year, 3 months ago, submitted by

gavinjoyce 1 year, 3 months ago

weblogs.asp.net — "One of the questions I get asked fairly regularly is: 'how can I can easily change different configuration settings in my web.config file based on whether my application is in a dev, qa, staging or production mode?' The most common scenario for this is one where an application uses different database connection-strings for testing and production purposes."

1 comment | category:

ASP.NET | Views: 10 | Get KickIt image code

tags: web.config, Tips, ASP.NET, ScottGuthrie | tag it

Everyones tags:

Your tags:

Please login or signup.

Add a live kick counter to your blog >> liveImage

You can even customize the image by choosing your own colors, and then clicking the button below to update the preview and the html code:

"Kick It" text
"Kick It" background
kick count text
kick count background
border

Simply copy and paste this HTML into your blog post.

Users who kicked this story:

gavinjoyce -

yesthatmcgurk -

tiernano -

reteep -

gt1329a -

samAdams - rocjoe71 -

korayem - joycsc - blisteringlunatic - dontera - senfo -

diamondz - baggyblack -

johnrummell - mehfuzh - schalkvanwyk

Comments:

Scott,

Great tips.

My situation is a little different and I was wondering if you have a suggestions for that:

My application uses a set of XML files as data source. I am deploying the same app on different servers where the location of the XML files differs from machine to machine I would like to prompt the user for the machine specific location of the XML files (or in general for machine specific data source information) during the install and make this information available for the app to use to access the data.
What is a recommended way of providing such machine specific information and how do you build it into the Web Setup Project?

I truly enjoy your tips and tricks and I would truly appreciate if you could provide me with a tip on my issue.

Thanks,
Niels

posted by nielskirkegaard 10 months, 3 days ago