Re: SourceSafe issues continued

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

The way I did it several years ago was for each developer to have his/her
own copy of the project file, and keep only the source files in VSS. We kept
only one person in charge of doing the official build, so whatever each
individual did with their own project file was up to them. It worked out OK.



"Ook" <usenet@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23YoE9q3RFHA.204@xxxxxxxxxxxxxxxxxxxxxxx
> 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.
>
>


.

Relevant Pages

  • Re: SourceSafe issues continued
    ... Our "build master" updated the master project (PJM) in VSS. ... Update Project goes from local VFP to VSS, ...
    (microsoft.public.fox.programmer.exchange)
  • SourceSafe issues continued
    ... Our "build master" updated the master project in VSS. ... It is very slow and causes the user doing so to check out the PJM, ... We can't "update project", because overwrites the PJM with old project ...
    (microsoft.public.fox.programmer.exchange)
  • Re: How to get PJM updates from VSS?
    ... " the network file I/O and data transfer slow down ... VSS, and it uses very little bandwidth. ... which is stored in a PJM file. ... Working with the project via SourceSafe is real pain. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: SourceSafe issues continued
    ... An updated local .PJM file is generated via SCCTEXT.PRG. ... This file is compared against the copy in the VSS database. ... which is an option when you do check-ins from the VFP ... Developer A adds or removes an item from the VFP project manager. ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Studio.net project sharing confusion
    ... Source control with VSS with database projects doesn't work really well. ... sounds like if you turned on multiple checkouts for the project file, ...
    (microsoft.public.vstudio.sourcesafe)