Friday, December 19, 2003 5:31 PM
Scott in this
post happened to ask Whats the proper way to remove an item from source control ?
I had faced this problem earlier which led to the investigation of what all information is stored, where and How using which a VS solution happens to know the bindings the solution maintains with a SCM.
Necessity is the mother of invention (read investigation). I didnt have vs.net on the box where I had to actually take the source solution & relevant files and strip them off so that I could bind them to another SCM tool.
This is what I happened to understand and I believe I havent missed out on any thing.
Vs.Net uses certain files + information that is stored as part of the project and solution files to interact with a SCM.
*.scc, *.vspscc, *.user, *.vssscc and *.suo
Any file which has SCC in its extension are used by the source control system to which the solution binding exists.
.user is the file which contains the user / client side relevant data which might be required by the SCM
.suo is the user preferences / user side solution object file which contain the information which is used while Vs loads the solution file.
If you find these files along with your solution / project folders, they should be deleted.
*.csproj or *.vbproj or *.*proj
These are project files. When bound to an SCM , these files contain lines beginning Scc. These lines should be removed from the project files.
*.sln
These are solution files. When bound to an SCM, these files contain a section delimited by the lines
GlobalSection(SourceCodeControl)
and
EndGlobalSection
This section should be removed from the solution file.