SourceSafe issues continued
- From: "Ook" <usenet@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 22 Apr 2005 13:34:51 -0700
Right, let's continue this topic because I'm still not clear on a few
issues. Our "build master" updated the master project (PJM) in VSS. We have
a dozen developers that need to update their project. How do they do this?
"Joining the project" is what we do because it is the only way we know how.
It is very slow and causes the user doing so to check out the PJM,
preventing anyone else from doing this. User A "joins" project. VSS
automatically checks out the PJM to this person. This is just not right.
User A does not need the PJM, and VSS should not check it out to them. User
B, C, D....J all want to do the same, but no one else can because you can't
"join" the project if the PJM is checked out to someone else. When this
happens, it takes all morning for everyone to get the most current project
because they have to do it one at a time.
We can't "update project", because overwrites the PJM with old project
settings. Update Project goes from local VFP to VSS, and we want to go from
VSS to VFP.
Getting latest does not update the PJT/PJX, and without an updated PJT/PJX
you cannot truely get latest from within VFP. Getting latest simply gets
latest version of files project is aware of.
We've been going back and forth, back and forth, and the tech leads want to
get rid of the PJM and just store the PJX/PJT in sourcesafe because (from
their perspective) the VSS/VFP interface is such a kluge. I'm not sure I
disagree, but then I'm not a VSS expert.
.
- Follow-Ups:
- Re: SourceSafe issues continued
- From: Fernando D. Bozzo
- Re: SourceSafe issues continued
- From: Paul Pedersen
- Re: SourceSafe issues continued
- From: Dan Freeman
- Re: SourceSafe issues continued
- Prev by Date: RE: Close application
- Next by Date: Re: how to delete a charecter thro' low level format
- Previous by thread: Close application
- Next by thread: Re: SourceSafe issues continued
- Index(es):
Relevant Pages
|