|
I'm
trying to find the correct combination of VS.Net configuration settings to
achieve the following behavior with vault:
I
want to be able to do a Get Latest version at the project level and have Vault
get the latest version of those files that I do not have checked out, and I
want to be able to do this without being prompted to allow overwrite more than
once. I have been able to achieve these requirements individually, but not at
the same time
- I
can set it up in such a way that it will prompt me to overwrite every file that
is newer in source safe than it is on my machine. This is not desirable on large
projects, or solutions with many projects that add up to a large number of files
that need to be overwritten.
- I
can set it up so that the command executes successfully and quietly, but it only
pulls files that are new to the project (files that I don't have local copies
of), and will not touch files that have been updated to a newer version by a
coworker in Vault.
- I
can set it up so that it will overwrite all local files silently, **even those
files that I have checked out**. I can't imagine when this would be a desired
outcome of a Get Latest instruction.
I
have played with different combinations of the Modified Working Copy and Set
File Time settings. I would prefer to maintain the setting to check out files
automatically when a checked in file is edited (providing that it will get
latest version from Vault, and overwrite the local copy). We don't use
offline-edit or multiple-checkout features that might require merging of local
files with the Vault repository. Is all of this achievable in Vault as it was
with the default VSS setting with the Replace Writable
option?
-Josh
| 
