All geek questions in one place

Does Visual Source Safe really have no renaming?

I am using Visual Source Safe on a new assignment and it is not so bad ... then I renamed the file.

I clicked on the warning prompts, ignoring the fact that by renaming the file I lost my whole story. Is this really so? I cannot believe that VSS does not support renaming.

I am reorganizing a lot of code and not correctly renaming the work.

Thanks for answers. I assume that VSS has renaming functionality, just not in Visual Studio. What, for example, is an application interceptor to rename a file in the original control?: /

+4
source share
3 answers

This can be done in SourceSafe, but this requires a little manual intervention:

  • First make sure that the file you want to rename is checked.
  • In SourceSafe, right-click the file and select Rename from the menu (or, simply, just press F2), and then rename the file.
  • This only renames the file in SourceSafe. You will need to check the renamed file in the working folder, and then delete the source file from your working copy to complete the renaming.

If you look at the history of files (right-click, then Show History or altenatively, Ctrl-H ), you will see that its entire history is not corrupted. Note, however, that SourceSafe will reference the file by its new name in all history entries for the file. Actual renaming is tracked at the project folder level. If you look at the history of the folder containing the renamed file, you will see a history element indicating that the file has been renamed from oldname to newname .

Addendum: note on finding older versions of renamed files from history

Joe White commented on this answer that SourceSafe does not respect the original file name when you do Get in an older version of the renamed file. This is true if you are getting an older version from the file history viewer.

However, if you use Get an older version of your code (before renaming) from the parent folder history viewer, SourceSafe will correctly use the original file name when it puts the files in your working folder.

The reason for this behavior is that SourceSafe tracks renaming at the parent folder level, not at the level of each file.

+8
source

It does not matter.

Once you notice that your SourceSafe database is corrupted without any action, the SS can produce daily rainbows and unicorns, but in the end they will turn into rotting sea creatures random bytes that cannot be restored by humans.

Get away from the security source. It was a noble effort by Microsoft to make people understand the idea of ​​version control, but I saw twice (after 2 years, the same data store, 3 people working against him) that he was dying from an irreparable death.

Come in svn, tfs, anything else! Tell your elders that you play with fire every time you register. Perhaps you are lucky that I was in the project before the unsuccessful one, or you could just finish ... based on your backup strategy ..

+3
source

VSS has a rename function that saves the history of File > Rename (I'm sure this history of mites) but it has been a long time since I used it

+1
source

Source: https://habr.com/ru/post/1286606/

More articles:


All Articles