Working Folder best practices

This forum is now locked, since Gold Support is no longer offered.

Moderator: SourceGear

Locked
JonShrout
Posts: 33
Joined: Mon Jan 30, 2006 10:43 am

Working Folder best practices

Post by JonShrout » Mon Apr 10, 2006 10:34 am

I'm trying to determine the pros and cons of multiple developers using the same working folder.

We would like our developers to use the same working folder for COBOL source code. The developers use a text editor to make their code changes. There is no compelling reason to use working folders in this way, it's just management's preference.

I would very much appreciate it if anyone could speak to the pros and cons of this approach and possibly to best practices concerning working folders.

Thanks,

Jon

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

Post by lbauer » Mon Apr 10, 2006 12:25 pm

Vault is designed on the premise that each user has their own working folder on their client machine. The Vault Client uses cache files and file baselines to improve performance and determine the state of the files in the working folder as compared to Vault tree.

If multiple users use the same working folder, you'll get unexpected results, such as renegade files, file status being out of sync, etc.
Linda Bauer
SourceGear
Technical Support Manager

Locked