"Move" a file in Sourcesafe - Best Practices question

[klyn610]

Hello

I have a small problem I'm hoping there is a solution to by using best
practices with VSS.

When we do a build of our software, we do a recursive Label, then a
recursive "get" based on that label. If for some reason in the future we
need to refer to a previous build, we can always view or do a "get" by the
label.

The problem is when a file gets deleted or moved from it's original
location. If we need to recreate a specific label of our code and a piece of
the code has been moved or deleted, we have an incomplete copy of the labeled
code. Also, deleted code does not have any history kept.

One solution is to "delete but not destroy" the file from it's original
location. This will retain the history and may produce the file if a
recursive get by label is done if the label was applied when the file
"existed".

We now have a need to actually move a piece of code from one directory to
another. I'd like to retain the history. If I do a "move" in VSS from the
old to new directory, the file appears "shared" in the new location. The
file does not appear in the old location, although it is there, just "deleted
not destroyed".

[Catherine Sea via DotNetMonster.com]

You can branch the files in VSS and then do the modification. In this way,
all histories remain.


Catherine Sea
http://www.scmsoftwareconfigurationmanagement.com/