We use configuration files within various projects under source control (TFS), where each developer has to make some adjustments in his local copy to configure his environment. The build process takes care about replacing the config files with the server configuration as a part of the deployment, so it doesn’t actually matter what is in the repository. However, we would anyway like to keep some kind of a default non-breaking version of config files in the repository, so that e.g. people not involved in the particular project won’t run into troubles because of local misconfiguration.
We tried to resolve this by introducing the check-in policy that simply forbids to check-in the config files. This works fine, but just because we’re lazy to always uncheck those checkboxes in the pending changes window, the question comes : is it possible to transparently disable the check-in of particular files without keeping them out of source control (e.g. locking their current version) ?
Your primary options:
There are a few other ways but I think these are the clear favorites.