0

The several different environments (e.g. live, demo etc) of my web app are differentiated by config settings in a folder called EnvironmentConfiguration. Whenever I update one of the sites, I delete the EnvironmentConfiguration folder from the precompiled site before copying the website files over (i.e. in order that the EnvironmentConfiguration folder in the deployment location is not replaced).

Just to save mistakes, is there a way I can get Visual Studio not to produce the EnvironmentConfiguration folder when it precompiles the site for me?

David
  • 15,750
  • 22
  • 90
  • 150

1 Answers1

0

You could try a couple of things.

1) Right click on the folder in the solution and select exclude from Project.

2) Look at each of the files in the folder and set the BuildAction property to 'None' rather than 'Content'

WraithNath
  • 17,658
  • 10
  • 55
  • 82
  • Thanks for your response. 1) The folder doesn't have the Exclude from Project option. 2) If the folder gets created, but not the contents, then an empty folder will be created which can still copy over a folder with the same name surely? – David Mar 02 '11 at 10:09
  • @David - The folder should not get overwritten even if its empty. I have a web application which is a main product, then sometimes there are amendments or extra pages for specific clients. I create a new web applicaiton and installer with the same folder names and install the second application after the first. Then the extra files get added to the folder rather then replacing the folder with only the contents of the second installer. – WraithNath Mar 02 '11 at 10:11