Vault client - baseline storage
Moderator: SourceGear
Vault client - baseline storage
The Vault (GUI) client stores a baseline copy of every file that's on the server. These files are apparently stored in CSIDL_APPDATA\SourceGear\Vault_1\Client. Is there any way to change the location where the client stores these baseline copies other than changing the location where my CSIDL_PROFILE directory resides? I'd prefer to have these baseline files saved on my development drive (alongside the working folders) rather than on the system drive. The dev machines here all have drives on sleds so a dev drive can be moved to a different machine if the machine fails. Having the baseline versions saved in CSIDL_APPDATA means that moving the dev drive to another machine would effectively break the vault client and force a re-get of everything.
-cd
http://download.sourcegear.com/misc/vau ... olders.htm
Store working folder data inside folders
Check Store working folder data inside folders if you want the _sgvault folders to be created within working folders. The files will be visible. You may want to do this if you are used to working with Vault 1.0.
Leave it unchecked to store the _sgvault folders within the users application data directory for the system. The folders will be hidden.
If you toggle this option back and forth, working folder data and status will be lost (files will become of Unknown status).
The default is Unchecked. If you do not know what to choose, we recommend you choose the default.
Store working folder data inside folders
Check Store working folder data inside folders if you want the _sgvault folders to be created within working folders. The files will be visible. You may want to do this if you are used to working with Vault 1.0.
Leave it unchecked to store the _sgvault folders within the users application data directory for the system. The folders will be hidden.
If you toggle this option back and forth, working folder data and status will be lost (files will become of Unknown status).
The default is Unchecked. If you do not know what to choose, we recommend you choose the default.
What has happened is the client cannot find the location of its state folders - since this option changes the location.GregM wrote:If you toggle this option back and forth, working folder data and status will be lost (files will become of Unknown status).
Which can be resolved by issuing a full get. A new Get (recursively, if necessary) will retrieve new baseline info, thus resolving the problem.
FWIW, if you plan on moving / renaming folders, I would take a long look at storing Working Folder Data within the actual working folder.
Jeff Clausius
SourceGear
SourceGear