D
dev648237923
I develop my application on my dev server and then I deploy it to a
customer's production server. I store the db connection string in web.config
(is this best practice?). When I deploy I have to open the production
web.config and change the connection string to the correct one for
production. Now I want my customer to keep their sql server
username/password secret. They are unable/unwilling to change the web.config
each time I make an update to the app. How can I deploy my app without
having to access their web.config (each time I deploy it overwrites
web.config). There must be a way a dev can make an asp.net app and deploy it
it to a server without always knowing and having to change the connection
string. Thanks for any ideas!
customer's production server. I store the db connection string in web.config
(is this best practice?). When I deploy I have to open the production
web.config and change the connection string to the correct one for
production. Now I want my customer to keep their sql server
username/password secret. They are unable/unwilling to change the web.config
each time I make an update to the app. How can I deploy my app without
having to access their web.config (each time I deploy it overwrites
web.config). There must be a way a dev can make an asp.net app and deploy it
it to a server without always knowing and having to change the connection
string. Thanks for any ideas!