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.
So I have a .net web application that I use the VS 2010 “publish” feature to deploy to a server. Each instance of the application has its own unique connection string, pointing to its own database.
I have 80 instances of this application. I would like to be able to update 1 instance with a “master” version of the app, and then have the other 79 update themselves, but keep their existing connection string.
What is the most common / standard way of achieving this?
Through the properties of the web.config file (solution explorer) you can set the “Build Action” to “none”.
Then deploy the webapp to a local directory. This is now without that web.config file.
Then copy that local directory over your 80 applications. You could maybe automate this step.