SourceGear Support

I moved this over to the new Dragnet discussion forum.

I've just created a new Dragnet category with the usual forums. For now, any questions about the test releases of Dragnet should go to the Support (Dragnet) forum.

Have you checked the return value of PromoteLabelItems? The Vault client API isn't as consistent as it should be with returning useful error codes (often it throws exceptions), but this function does return the server's status code. You can translate the number to a message with code like: int retur...

Although both approaches will work, the second one uses the promotion API specifically designed for this kind of thing. Are you having any problems getting your code working?

"Store working folder data inside working folders" will start storing all the baseline files and the state file with version information inside the working folders (in an _sgvault subfolder). We don't recommend doing this so multiple users can share working folders, since it's untested, bu...

You don't want to delete the whole GUID-named folder if you just want to remove the cached repository structure. See this KB article for the specific files to delete (CacheMember_LastStructureGetTime and CacheMember_Repository). Deleting the whole GUID folder will remove baseline files and version i...

In %APPDATA%\SourceGear\Vault_1\Client, there is a folder for each repository you've connected to. Its name is a GUID. Inside each of these is a folder named after the user you connected as. Inside of this folder will be a folder called "_sgvault", which contains all of the old baseline fi...

It was the DST change. Windows always reports its filesystem modification times in local time, which means whenever a computer's time zone changes (including adjustments due to DST), Vault is told the file times have changed, compared to their old values. Vault 3.0 fixes this by storing modification...

Yes, you can always switch the time zone momentarily back to check in your changes. There's really no other good work-around for Vault 2, but the bug is fixed in Vault 3.0. 3.0 Details: Vault 3.0 will convert Vault 2.0 format working folders to a new format, but since no time zone was saved in the o...

It sounds like Vault is working properly. Folders retrieved using -destpath should not be used as a working folder in any Vault client. They lack all of the information about file versions and times that Vault needs to determine a file's status. When a Vault client is told to use a disk folder that ...

Vault 2 uses filesystem modification dates to determine whether a file is modified (Vault 3 offers an option to use CRC32). It sounds like the dates on the files are changing (perhaps a build tool is touching the times), or the command-line client isn't storing the "modification time at last ge...

Are you changing time zones (or possibly daylight saving settings) when these happen? Vault 1 and Vault 2 don't compensate for changes in timezone (and DST) that cause Windows filesystem times to "change" when scanned, and the result is similar. Vault 3 fixes this bug. Are these files real...

I didn't catch it until it was too late that you're using VB. My example is written in C#, but the code is so simple (and the Vault functions and types are all identical) that it should be very easy to translate to VB. Let me know if you want any help understanding the C#. Also, the project file is ...

I wrote some example code for listing and adding users. Vault's design doesn't permit deleting users once they've been added, because of the effects that would have on the history of the objects in the repository. You'll need to drop your DLLs from your client installation into the Client DLLs direc...

Vault stores its working folder information in a similar way to CVS. CVS creates a directory named "CVS" inside each of its working folders, and puts some state information there. Vault creates a directory called "_sgvault" in the user's Windows application data folder, one for e...