
28
|
Chapter 1, Master Projects and Solutions
#5 Remove SourceSafe Bindings
HACK
HACK
#5
Remove SourceSafe Bindings Hack #5
Visual SourceSafe comes bundled with Visual Studio for free, so it is one of
the most popular source code control programs for Visual Studio developers.
However, it will leave cruft in your source tree that you might want to get rid
of if you send your code elsewhere.
In order to do its job, SourceSafe adds some XML elements to the Visual
Studio solution and project files and adds some source control files to each
project directory. These changes are transparent when using SourceSafe, but
cause problems when sharing the solution with someone who does not use
SourceSafe or someone who does not have access to your SourceSafe data-
base. It could also cause problems if you are attempting to change your
source code control provider from SourceSafe to something else, like CVS or
Subversion.
Removing Bindings
You must change two things to remove all SourceSafe bindings. The solu-
tion file and all project files must have any source control information
removed, and any files ending in .scc must be deleted. To do this, the Visual
Studio solution and project files must not be in use, so close down the
Visual Studio IDE.
It is best to make a copy of the entire Visual Studio solution
before hacking any files. If something goes wrong, you
should have a backup.
Visual Studio solution files are