0

I have heard some pretty bad review about source safe (VSS) but no real examples. Anyone have a good example/story?

dewalla
  • 1,317
  • 8
  • 18
  • 42
  • 1
    sure - not the place for that, though. Basically had to move to a new repository for a medium size project every 4-6 months (and loosing all the history up to then) due to fragmentation and data corruption - for a whole three years! – marc_s Aug 02 '10 at 19:32
  • 1
    If you are being nagged to move to git or svn or TFS and think that VSS is good enough, go try to export your repository. If you can't export it, then it is safe to say the source control tree is corrupt, despite what Analyze is saying. http://stackoverflow.com/questions/1039583/detecting-vss-corruption-through-export-to-svn The real horror story in my opinion with VSS is that users lock files, which is drag on productivity while dev wait for other dev to unlock those files. – MatthewMartin Aug 02 '10 at 19:34
  • 1
    Duplicate of http://stackoverflow.com/questions/520926/any-real-life-visual-source-safe-horror-stories – JohnFx Aug 02 '10 at 19:36

1 Answers1

2

VSS: No warning for conflict when you do checkin. My colleague used to eliminate my changes. And then I had to drill down into comparing version histories for the check-in he did. He just used to ignore each time :(

ankitjaininfo
  • 11,961
  • 7
  • 52
  • 75