I've been using SourceSafe since before it was purchased by Microsoft,
and I'm not sure I've seen what you are seeing. I would suspect a
configuration or operation problem, although I'm not sure exactly how it
happens.
Proper maintenance of SourceSafe is essential. Most of my configurations
run analyze daily, "fix" runs once a week, physical file list generation
and other processes frequently. Journaling of changes, shadow folders of
results, and daily backups are all part of the maintenance plan.
I have clients with dozens of developers and literally millions of lines
of source code who depend on SourceSafe (and SourceOffSite in many
cases) as a mission-critical component in their software development
process.
That said, if it's not working for you, there are a number of other
contestants out there, such as Starbase Versions, PVCS and CVS. Starting
over with a new system may be appropriate if you feel you've been burned
with the old one.
-----Original Message-----
From: profox-bounces (at) leafe .D.O.T com [mailto:profox-bounces@leafe.com] On
Behalf Of Lou Syracuse
Sent: Thursday, July 31, 2003 12:30 PM
To: profox (at) leafe .D.O.T com; profoxtech@leafe.com
Subject: RE: What do YOU use besides VSS for source control with VFP?
Don't worry, I'm not going to jump on you for being a MS zealot Chuck.
:)
The problems we've had are modifications that mysteriously 'disappear'.
We
have had several instances where we modify code and release an EXE, then
later we will modifiy more code and release a new EXE - only to hear
from
our customers that the old modifications are GONE. We look in the
code
and sure enough, those changes aren't there.
We're a small shop, the builds are always done on the same machine and
the
'builder' always does a GET on all files. Right now we're down to one
Source Off-site user and me in the office using the integrated VSS
options
within the VFP IDE. Since the other developer left I get to do the
builds....
My guess is that the Admin doesn't run Analyze very often, if at all.
Could be the problem? I've never played much with VSS outside of
checking
in/out code...
We just can't afford another debacle like we had last week,
reintroducing
bugs we fixed previously.
>From: "Chuck Urwiler" <chuck (at) eps-software .D.O.T com>
>Reply-To: profox@leafe.com
>To: profoxtech (at) leafe .D.O.T com
>Subject: RE: What do YOU use besides VSS for source control with VFP?
>Date: Thu, 31 Jul 2003 11:05:55 -0500
>
>Hi Lou,
>
>What VSS problems have you had? I've used VSS at my previous job and
>currently use it at EPS. As long as you do the recommended maintenance
>(doing Analyze every once in a while) you should be in good shape. The
>only trouble I recall is having a DB that was just "too big" for a
>reasonable analyze run, but were able to solve that by moving some of
>the projects to a new VSS database.
>
>Oh, and I currently do ALL of my VSS access with Source Off Site. Works
>great.
>
>So, I guess my vote is to stick with VSS, but I'm sure I'll get jumped
>on for being an MS zealot or something. <bg>
_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*.
http://join.msn.com/?page=features/featuredemail
[excessive quoting removed by server]
©2003 Ted Roche |
