May 19, 2010 10:50 PM|tboswell|LINK
I thought we found a good way to handle this using the following attribute in the web.config
<connectionStrings configSource ="connectionStrings.config">
This allows us to put the developer specific configs in a separate file (that is not under source control). The file checked into source control is the same for everyone and is void of connection strings. Each developer has their own copy of "connectionStrings.config"
which is not checked into source control.
However, when we try to run unit tests using this technique we get an error such that the unit test project can't find the configSource file. But it works well otherwise.