Menu
After a repository is imported from VSS to SVN, there are some files which I guess might be VSS specific - .vsssc and .vssscc files for the solution and .vspscc for projects. They seem to be related to VSS project binding. Are they needed (or useful) for SVN as well?
318
Source Code Control (SCC) file for projects created with Microsoft Visual Studio; contains metadata used for tracking revisions of Visual Studio software development projects; includes information such as the version number, file path, and the number of nested projects.
The vssscc/vspscc files are needed, especially for TFVC. Among other things, they hold the list of local files that are explicitly excluded from source control (i.e. . tfignore). We cannot eliminate these files.
The .vsssc and .vspscc files contain references to the visal sourcesafe server in which the solution/project was kept. Subversion doesn't need this information as this information (and more) is stored in the .svn areas of your working copy.
For the data in the .sln and project files it depends on whether you use AnkhSVN, VisualSVN or neither.
AnkhSVN (2.0+) is a real SCC provider and allows (optionally) marking the projects as managed by Subversion (/AnkhSVN). This will add similar SccXXX lines to the project files as VSS did, but will make all projects send information to AnkhSVN.
VisualSVN doesn't mark projects and tries to handle everything from the subversion administrative area by itself.
171
No. No they aren't
20
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
