quote:Original post by Dean Harding

SourceSafe can do all four of those things...

quote:Original post by felonius

quote:Original post by Dean Harding
SourceSafe can do all four of those things...


No it cannot. If have used both system quite a bit at work.

In source safe rolling back and taking snapshots of old files can only happen for one file at a time. You cannot give one command and get a snapshot of the whole system unless you where so foresigted to actual put at label at that specific point of time. In Perforce you just give it a time and date and get the whole system (or a subset if you want to).

In source safe the performance will go down to a drag if you add graphic assets too. It will get so slow you regretted doing it. I tried. Many users of source safe, supplement it with ALien Brain from NxN for this exact reason (although the version of ALien Brain we tried here didn't scale well, but NxN claim to have fixed that issue in the meantime)

Temporary branches in source safe does not work very well. It is quite complicated to make a brnach and then get a copy of that in another working directory - and then work on both at the same time. When you do a branch in perforce you can have group of people work on that branch as nothing had happened and then later they can merge together as nothing had happened. SOurce safe is very good at the actual merging of cpp files though - better than perforce.

quote:Original post by mrhollow
I have never used SourceSafe, so couldn''t say for certain, but it''s my understanding that SourceSafe is limited to VisualStudio type projects. Again, I have no direct experience, so that''s only hearsay.

quote:Original post by mrhollow
It makes great sense for people developing on more than one machine, or across different platforms, windows, linux, etc...