Skip to main content

Having different config for local dev and remote deployment for web.config

I have been maintaining 2 different Web.Config files for ages, one for developement and one for live or remote deployed sites.

This is to say the least a pain. When you deploy your website you then need to remember to either copy the old config and replace or you need to edit the live one with the correct connection strings and the like.

While looking for a solution to a security related problem on a deployment of an ASP.NET site I came across this site:

http://www.troyhunt.com/2010/11/you-deploying-it-wrong-teamcity.html

2 Web Config files...

The essence of this shows how you can have a core web.config then you can have a debug web.config and a depolyed web.config.

To do this all you do is in your Visual Studio project simply right-click the web.config file and select "Add Config Transforms". If it is greyed out / disabled then check if two  files exists under Web.Config

One called Web.Debug.Config and once called Web.Release.Config.

These two files let you add anything in the file that is specific to that deployment, when writing codce the Debug.config is used and when deploying the web.release.config is used.

COOL hey, wow that prevents a lot of work.

Just a few things to note:
  • weg.config is essentially the local copy of web.config. When you deploy web.release.config is the master
  • Look at the demo strings in the files, you do not move the app settings into the Web.xxx.config, rather you replace it using xdt:Transform="SetAttributes" xdt:Locator="Match(name)"
  •  

Comments

Popular posts from this blog

Bitcoin / Cryptocurrency – what is it and how can I benefit

What is it I started investigating Bitcoin when it was worth just over $1000 a bitcoin. I was interested in what it was and how it worked. A lot of people are saying we missed the boat, but I believe that everyone should at least try put a little money in now, or at least use a faucet (see below) to make a little micro-currency. You can read a Wiki article about bitcoin and its history etc. But what you need to know is that it is a currency, that is independent of country. No one really knows who invented the concept of a cryptocurrency since the person who published the paper used a nom de plume. All new cryptocurrencies work more or less the same way as Bitcoin. So as I explain below I interchange these terms. Bitcoin is the original cryptocurrency. How Bitcoin works The currency releases a coin based on a mathematical formula. There will never be more than 21 million bitcoins (other cryptocurrencies do not work like this). Each bitcoin can have divided into one hundred mil...

iTunes song purchased on iPhone not showing in the library, only show purchased

I recently purchase an album on my iPhone, and then when I wanted to mke sure it was in my iTunes library it was not there, but in the Store I found it and it said purchased. If I clieck on Check for Available Downloads, it said nothing. After some search i found this: https://discussions.apple.com/thread/5551143 Which had this fact: " Music can't be redownloaded in all countries, so depending upon where you are you might not be able to redownload music. If music does show as a category, but not that album, then is it hidden :   http://support.apple.com/kb/HT4919 " I then connected my iPhone and saw that to copy a purhcase your computer's iTunes via File > Devices > Transfer Purchases

Access conversion NOTE1: default DateSerial in VBA/Access to SQL

I have started slowly converting my Access database to SQL. The reason is that I would like to take the application online. After trying to use Access's (version 2007) transfer tool, which did not work that well. I found Microsoft's SQL Migration Assistant 2008 for Access, nicknamed SSMA. Which you can download here . When you install there is a niggle about the license, which you need to download into their specified directory and it must be the name they provide. So about the create table. My one table would not convert and I could not see why. After looking at the SQL command I saw the problem was the use of DateSerial. I googled a few sites and could not find an answer The CREATE TABLE line was: [RequireUntilDate] datetime2(0) DEFAULT DateSerial(1980,1,1) NOT NULL, I clicked on the whole command and copied it and then in SQL Server Management Studio, I tried to create the table and found that if I specified the date in US date format it worked: [RequireUnti...