Question

Currently I am using a shared database model for our development. I know, it’s better to use local development databases to do database versioning the right way without one developer breaking everyone else’s code. So that’s what I’m trying to get to. I have a question about the web.config file though. How do I ensure that once every dev has his own local development database, he doesn’t have to manually change the DB connection string every time he gets an update from source control? What’s the best way to do this?

For example, say Johnny Dev commits his web.config that holds a connection string like this:

server=JohnnysBox;database=JohnnyAppDev1;

So now Susie Dev gets an update and she has to change her connection string to this:

server=SUE;database=development;

So now Susie and Johnny keep committing their own connection strings to the web.config file, and every time they get an update, they have to change the connection strings in all applications.

What’s the best way to handle this situation so that devs don’t mess up each others’ connection string settings, but can push other kinds of config file changes to all the other devs when necessary (like a new app setting)?

Answer 1

For configuration or settings files, what you need to version is:

• a template files (server=@USER_NAME@;database=@DATABASE_NAME@;)
• one or several value files
• one script able to replace the variables by the right values