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

I would agree.  I can't think of any good reason to not prevent it.  I
think most of us (maybe I'm wrong) would *expect* for this to not be an
option.
 
On the note about Chris' specific issue, isn't that a bug?  If "Prompt
on Overwrite" is enabled, that's exactly what it should do, no?
 
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Jan C. de
Graaf
Sent: Wednesday, March 03, 2004 2:36 AM
To: 'Chris Mullins'; [email protected]
Subject: RE: [vault-list] Prompt for Overwrite does not work in VS.NET
Integration


Chris pointed out once again how rediculously dangerous it is to be
actually able to do a 'get-latest' on a checked-out file! If feel Vault
should AT LEAST warn at the first already-checked-out file it
encounters!
 
What reason is there to do a get latest on a checked-out file? Maybe on
a per-file basis, but certainly not on the (recursive) directory level.
 
Jan C. de Graaf
New Limit Database Solutions
 
 
 
 
-----Oorspronkelijk bericht-----
Van: [email protected]
[mailto:[email protected]] Namens Chris Mullins
Verzonden: woensdag 3 maart 2004 6:27
Aan: [email protected]
Onderwerp: [vault-list] Prompt for Overwrite does not work in VS.NET
Integration
 
Open a project in Source Control
 
Make a bunch of changes.
 
Right-Click on the Solution, and (by mistake) click "GetLatest" instead
of "Check In". Think for a moment "Do I kill the process or let it
finish?". 
 
All checked-out files are overwritten. 
 
 "Prompt on Overwrite" is enabled in the Vault GUI. 
 
-- 
Chris