Team Development with Visual Studio Team Foundation Server

System.Configuration.ConfigurationManager class. In the WinForm application,
you must add a reference to System.Configuration.dll explicitly.
using System.Configuration;
private string GetDBaseConnectionString()
{
return ConfigurationManager.ConnectionStrings["DBConnStr"].ConnectionString;
}
4. Ensure that the User.config file is deployed along with the application code. To do so
in Solution Explorer right click the User.config file, click the Properties and then in
the Properties pane, set the Copy To Output Directory property to Copy if newer.
Do not add the User.config file to source control. In this way, each developer and the
test team can explicitly specify the connection string through their own User.config
file. Source control may contain other User.config files, for example for testing and
for production. These files should be managed by the users responsible for managing
the testing and production environments. These test and production User.config files
should not be stored as part of the database projects but should be in different areas of
the source control system.
In source control you should have a User.config file for each of the environments that
you use, such as production and test. These configuration files should specify the
connection string for the database. The User.config file must be present for the
configuration system to work.
Tip: By default, the user configuration file is automatically added to source control when
you add the solution. To prevent this, when you first check in the files, clear the
User.config file check box. You can then right-click on the file in Solution Explorer and
select Under Pending Changes to ensure that the file never comes under source control.
It is important to understand that if you are using this mechanism, the User.config file
must be present. Somebody needs to be responsible for ensuring the environment is
correct when creating builds for production releases and for any test environments. As
part of this build setup, the appropriate User.confg file will need to be retrieved from the
source control system and copied into the correct location for MSBuild to be able to find
it.
Summary
When managing projects or third-party assemblies, you can use either branching or
workspace mapping. Branching is the preferred approach because it stores the
dependency relationship on the source control server. Using branches enables you to
make a conscious decision to pick up updated binaries or source.
Workspace mapping is a client-side-only approach, which means each team member
needs to create the mapping on their own computer as well as on the build server in order