First, let me compliment you on your product.
Now a big annoyance. I want the recursively get a number of files (and over-ride all working folders) - just like I could do in VSS. Why can't I do this with Vault.
I have included a sceen capture from the VSS window.
In general, I have found that whenever I have an annoyance with Vault it is where you have changed the behavior from VSS. If the new behavior were actually better, I would not mind - but often times your approach has glaring deficiencies to the VSS way.
Thanks,
Travis
P.S. I also get headaches using your diff tool - I'll save that message for another day.
getting multiple files
Moderator: SourceGear
-
- Posts: 25
- Joined: Wed Apr 21, 2004 3:10 pm
getting multiple files
- Attachments
-
- getmultiple.doc
- (30 KiB) Downloaded 674 times
You can do a Get to a non-working directory with Vault.
The To box defaults to the working folder but can be changed by typing a new folder in the box or using the Browse button to locate a new folder. This can be a recursive operation.
The difference between this and VSS behavior is that changing the To: folder in Vault does not reset the working folder – it just overrides where files go for a particular Get Latest Version.
You would need to reset the working directory as a separate operation in Vault.
I can log this as a feature request for future consideration.
The To box defaults to the working folder but can be changed by typing a new folder in the box or using the Browse button to locate a new folder. This can be a recursive operation.
The difference between this and VSS behavior is that changing the To: folder in Vault does not reset the working folder – it just overrides where files go for a particular Get Latest Version.
You would need to reset the working directory as a separate operation in Vault.
I can log this as a feature request for future consideration.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
It doesn't do this in VSS either, and I personally think it should stay the way it is in Vault.lbauer wrote:The difference between this and VSS behavior is that changing the To: folder in Vault does not reset the working folder – it just overrides where files go for a particular Get Latest Version.
You would need to reset the working directory as a separate operation in Vault.
I can log this as a feature request for future consideration.
If a subfolder has a working folder, will the GET go to the working folder for that subfolder, or to a subfolder of the new folder specified in the dialog? VSS allows for either behavior (see the "build tree" checkbox).lbauer wrote:You can do a Get to a non-working directory with Vault.
The To box defaults to the working folder but can be changed by typing a new folder in the box or using the Browse button to locate a new folder. This can be a recursive operation.
-
- Posts: 25
- Joined: Wed Apr 21, 2004 3:10 pm
If a subfolder has a working folder, will the GET go to the working folder for that subfolder, or to a subfolder of the new folder specified in the dialog? VSS allows for either behavior (see the "build tree" checkbox).
When I ran a get - subfolders went to the working directory not the "new" subtree. VSS implementation of having choice is far better.
When I ran a get - subfolders went to the working directory not the "new" subtree. VSS implementation of having choice is far better.