Is it possible to configure a WebSetup project to not overwrite config files?
Why? We have several websites that runs in both staging and prod and I would like to have one installer instead of one for staging and one for prod.
/Carl
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve done some googling and it seems like there are a bunch of different solutions to separate staging settings from prod settings. And this way might not be the best.. It’s more of quick and dirty solution.
This is how I solved it.
Now the file will stay on the server when you remove the Webapplication.
So change it to prod settings, and the next time you will deploy your awesome Webapplication it will not overwrite the existing config file(s).
The big downside of this is that you have to add new settings manually to the config files when add new settings in the application.