working folder storage location

[lyle.dodge]

Where is the working folder's location actually stored using Vault? i.e. when i set the working folder for $/Foo to c:\Foo, then uninstall Vault Client, then reboot my computer, and install Vault Client, the working folder is still set. Before reboot I removed c:\Foo. Is the list of working folders kept in the vault database, if so, which tables? Or is it being kept in isolated storage by the Vault Client?

[sterwill]

Vault doesn't use isolated storage for any of its settings any more (we had too many problems with it). The file you're looking for is called CacheMember_WorkingFolderAssignments, and its exact location depends on a few things (your Vault username, repository GUID, etc.). Read this KB article for details finding this file.

If you're uninstalling Vault (to be re-installed later) and don't wish to preserve any local configuration information (since you deleted your working folders), you can safely delete the entire %APPDATA%\SourceGear\Vault_1 directory.

[lyle.dodge]

What normal operations trigger this folder to get cleared out? I just checked the size of that folder on my computer, and it's 952MB. That doesn't bother me, but there are some older laptops that are being used by other team members. Is there a cleanup option in the GUI clients for clearing out this information? That way if they're in the office, they can get latest and clear out this data before they take off.

[sterwill]

Currently there is no feature to do the cleaning. It was always intended to be included with an early version of Vault, but other features took priority, and the work-around for setting new working folders (although not automatic, and not simple), has kept people going thus far.

[lyle.dodge]

I wrote this up to deal with the unsetting of working folders. It's a console application which will prompt you for host, repository, user, password, then call the Vault Client to UNSET the working folder for all repository folders except $.

I put this in an installer so all of our devs can use it from time to time, to make sure that nothing is mucking up their working folder locations (bad visual studio .net...)