Improvement: Locally Modified File

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
Tor-A-J

Improvement: Locally Modified File

Post by Tor-A-J » Wed Jan 12, 2005 5:53 am

When I open a Visual Studio project with 'Get latest' from Vault, and one or more of the files has been 'Checked out' and modified by another open project, the 'Locally Modified File' dialog comes up with:

'Owerwrite' set, and 'Apply to all subsequent files' not set.

This is ok when a file is modified, but NOT 'Checked out'...

When a file is 'Checked out' and modified the dialog should default to this:

'Do not overwrite/Merge later' set, and 'Apply to all subsequent files' set.

Then a simple push on OK will prevent loss of intended modifications by another project!

This is how the Visual SourceSafe is doing it, and it is the best way to do it...





[/img]

Guest

Post by Guest » Wed Jan 12, 2005 8:13 am

We've had other requests for this and it's logged as a feature request in our database. I'll add your "vote."

Linda Bauer
SourceGear
Technical Support

Post Reply