GetLabeledFolderToNonWorkingFolder and NewBulkMessages

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

Moderator: SourceGear

Post Reply
michaelF
Posts: 6
Joined: Thu Apr 27, 2006 8:56 am

GetLabeledFolderToNonWorkingFolder and NewBulkMessages

Post by michaelF » Thu Apr 27, 2006 9:10 am

[sourcegar vault version 3.1.8.]

With the API, a call to GetLabeledFolderToNonWorkingFolder(...) makes the BulkMessage handlers to receive a " Fetched file.ext" for all files in the the folder with the specified label, regardless if the latest version of the file is already present on the local folder or not. Is it possible to receive only the list of files that have changed (retrieve only the files that are different)?
Note that getting labeled folder to working folder make correct messages to be handled.

With client application, the behavior seems to be identical:
1. Select a folder.
2. Right click & show labels.
3. Right click on a specific label and get
4. Select a different folder (ex C:\tmp)
5. Repeat 1 to 4 steps. Messages tab display a "Fetched file.ext " message for all files again.

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Thu Apr 27, 2006 9:28 am

This is expected behavior for a get to a non-working folder. It's intended to be a fresh get to a location outside the working directory.

Vault has an elaborate system of client side cache files, hidden state folders with baselines files, etc., to determine file status in the working folder.

When you do a get to a non-working folder, there is no such mechanism.
Linda Bauer
SourceGear
Technical Support Manager

michaelF
Posts: 6
Joined: Thu Apr 27, 2006 8:56 am

Post by michaelF » Thu Apr 27, 2006 10:12 am

Ok. Thank you for your answer.

Post Reply