Bill,
I've been using VSS about 4 years now, pretty much problem free. One of my
only pet peeves is that it doesn't offer a web interface as of 6.0 (without
a third party tool).
I'm interested in how you got pinning to work. As I understand it pinning
allows you to create a link to a label correct? Unfortunately I have never
been able to successfully get pinning to work. Also do you, or you VSS
admin, run analyze often on your database?
TIA,
Duane
-----Original Message-----
From: Bill Grover [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 18, 2000 7:49 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Source Control
I figured I would stick my nose in here. Having not used the Perforce
product I can not speak good or bad about it.
We use Visual Source Safe and have been for about 3 years. Everything the
other users are saying about perforce can be said about source safe.
Depending your configuration of source safe you can allow multiple people to
checkout the same document. Then as each person checks the document in
source will compare what is being checked in with what is currently in
source safe. If you changed a line(s) of code and no one else has then
source safe simply merges your changes automatically. If however, you
changed some lines and someone else changed the same lines it will show you
the 2 versions and allow you to choose which set of lines to place into
source safe. Once "merged" you can even tweak the lines to get them into
their final form.
The only restriction on the multiple checkout function is for files that are
binary, for example Word documents, graphics, etc. In this case since it
doesn't have text to display differences with it will only allow one person
to have them checked out at once.
We have been very happy with source safe. We have had as many as 6-8
programmers working on 1 project simultaneously merging changes and adding
files without any problems. We have even taken advantage of going back into
the history and pulling a previous version of a file when someone "screwed
up" the current version. You can even "pin" versions. In this case you can
take a specific version of a file and this is the one retrieved whenever you
get latest version. However, I can have a later version checked out and
working on it. In this way if you have a routine that is stable and working
you pin that version. You can then enhance and add functionality to a later
version without worrying about corrupting someone else's application. This
usefulness comes in to play when you allow multiple projects to share the
same program.
Good luck with your decision!
______________________________________________________
Bill Grover
Supervisor IS Department Phone: 301.424.3300 x396
EU Services, Inc. FAX: 301.424.3300 x1396#
649 North Horners Lane E-Mail: mailto:[EMAIL PROTECTED]
Rockville, MD 20850-1299 WWW: www.euservices.com
______________________________________________________
> -----Original Message-----
------------------------------
Date: Mon, 17 Apr 2000 17:30:19 +0100
From: "Reid Philpot" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: RE: Source Control
Message-ID: <[EMAIL PROTECTED]>
I am that "London Developer" and can't agree more with what Scott has said
(and I'm not saying this just because he's my boss), Perforce is a wonderful
product which has made a potentially difficult situation very easy. Other
great features include being able to skip back to previous changes in the
documents history so you can eradicate any error your boss may have made.
:-)
<snip>
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.