Remove SourceSafe Bindings #5
Chapter 1, Master Projects and Solutions
SCC within the opening CSHARP or VisualBasic XML tag. In the preceding sam-
ple file, the four lines starting with
SccProjectName, SccLocalPath, SccAuxPath,
SccProvider would all need to be deleted. Save the file and close Note-
pad. You will need to do this for each project file in your application.
With Visual Studio 2005, the project file is a completely different format (it
is now based on MSBuild), but the data you will need to delete is very simi-
lar. Here is the relevant section of the project file:
<Configuration Condition=" '$(Configuration)' = = '' ">Debug</
<Platform Condition=" '$(Platform)' = = '' ">AnyCPU</Platform>
In this example, the elements named SccProjectName, SccLocalPath,
SccAuxPath, and SccProvider would all need to be deleted.
The last thing to do is remove all the files that SourceSafe creates with the .scc
extension. Every directory will contain a file called vssver.scc. Folders with
project files will have an associated mssccprj.scc file. There are also files end-
ing with <Project Name>.csproj.vspscc (vbproj if it is a Visual Basic Project) or
<Solution Name>.etp.vspscc. All of these files should be deleted, and with
that, your application will have all the SourceSafe bindings removed.
Hacking the Hack
I have written a simple Windows application that automates the removal of
SourceSafe bindings using the previous steps. You can download the latest
version from http://workspaces.gotdotnet.com/SourceSafeBindingRemover.
You can see this application in Figure 1-16.
Using it is simple. Select the solution root folder using the Choose Folder
button and click the Remove SourceSafe Bindings button. If the Remove
Bindings? checkbox is unchecked, then the window will show you a pre-
view of all the files that will be deleted. This will help you make sure that