14 messages in com.perforce.perforce-user[p4] VSS vs Perforce
FromSent OnAttachments
Peter Hecht21 Feb 2002 08:19 
Jim Fagan21 Feb 2002 08:31 
Jeffrey Jensen21 Feb 2002 08:43 
Steve Bennett21 Feb 2002 09:31 
Ken Rice21 Feb 2002 09:40 
Cat Gough21 Feb 2002 09:51 
Eivind Hagen21 Feb 2002 10:04 
Paul C. Pharr21 Feb 2002 10:32 
David Markley21 Feb 2002 11:04 
Maurice Meyer21 Feb 2002 11:10 
Ed Mack21 Feb 2002 11:11 
Chuck Karish22 Feb 2002 01:23 
Chuck Karish22 Feb 2002 01:29 
Chuck Karish24 Feb 2002 10:00 
Subject:[p4] VSS vs Perforce
From:Maurice Meyer (maur@openwave.com)
Date:02/21/2002 11:10:13 AM
List:com.perforce.perforce-user

Oh, and don't forget VSS' rediculous notion of labels. You can use the same label name on a project (like a directory tree) and on a particular file. But, depending on how you access it, you may get something different. And, you can't really update a label too well since it's really just a recording of a timestamp.

I only had a brief experience with VSS and found it to be a joke. And yes, they had been doing regular repairs of the DB when they asked me to take over VSS. I declined.

Really, VSS is a bit of a joke. Read the help page on labelling and the database repair tool...

Maurice

-----Original Message----- From: perf@perforce.com [mailto:perforce-user-admin at perforce.com]On Behalf Of Eivind Hagen Sent: Thursday, February 21, 2002 10:05 AM To: 'Peter Hecht'; 'perforce-user at perforce.com' Subject: RE: [p4] VSS vs Perforce

Perforce is REAL CM, VSS is just FAKING it...

The reasons we switched:

1. Changelists 2. Multiple Changelists 3. REAL Branching & Integration 4. Speed 5. Remote access (from Thailand, think slooow connection) 6. Price

The only reason why we would even consider staying with VSS is "because everyone knows how to use it", but that's not a very good reason.

-Eivind

-----Original Message----- From: Peter Hecht [mailto:peter.hecht at pplusic.com] Sent: Thursday, February 21, 2002 8:20 AM To: 'perforce-user at perforce.com' Subject: [p4] VSS vs Perforce

Hello,

I have to contend with a user who thinks Visual Source safe is the way to go. We are a microsoft based shop, using Visual FoxPro. Soon we will add SQLServer 2000 and Visual Basic.

How can I stop the Microsoft VSS movement? How is perforce better?