RE: Prompt for Overwrite does not work in VS.NET Integration

MessageYou can simulate this by setting the option for what to do when
Getting on top of locally modified files to not overwrite them.    Then,
whether a file is checked out or not, it won't be overwritten when you do a
Get if it has been modified locally.

 -----Original Message-----
From: [email protected]
[mailto:[email protected]]On Behalf Of Jan C. de Graaf
Sent: Thursday, March 04, 2004 2:56 AM
To: 'Dan Schreiber'; 'Monte Kalisch'; 'Chris Mullins';
[email protected]
Subject: RE: [vault-list] Prompt for Overwrite does not work in VS.NET
Integration


    Reply to the note below from Dan:



    I agree with the usefullness of the situation you describe. However if I
've setup Vault to require exclusive checkouts (in my opinion the ONLY way
to work) the whole scenario doesn't AND shouldn't apply.





    As for allowing Gets on checked out files - this is actually extremely
useful when multiple people are modifying the same file.  You want to be
able to merge other people's changes into your working copy without having
to do it as part of a checkin operation (so for example, you can merge some
interim changes into your file without having to check in yet, if you are
not ready yet).  This is the default setting for Get latest (to merge server
changes in, which leaves your file alone if there are merge conflicts).