Former VSS user, confused by differences

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

Moderator: SourceGear

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: Former VSS user, confused by differences

Post by Beth » Fri Nov 08, 2013 3:30 pm

I've logged a feature request for this functionality.

F: 17472
Beth Kieler
SourceGear Technical Support

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

Re: Former VSS user, confused by differences

Post by lbauer » Tue Nov 12, 2013 5:11 pm

The fact that the files are read-only should - by definition - mean that they can be overwritten by Vault without warning, without default options being considered at all. Just overwrite the files please (because they're read-only, meaning that they're not writable - they're not in edit mode - they're not checked out - they are fully available to be updated).
Vault is a replacement for VSS but isn't exactly like VSS because we've incorporated features which give users more options for development style.

For instance, Vault supports CVS mode (edit, merge, commit), where all files in the working folder are writable, and files don't need to be checked out before editing. The behavior described above wouldn't be applicable to those users.
Linda Bauer
SourceGear
Technical Support Manager

Mordachai
Posts: 84
Joined: Sun Feb 24, 2013 11:58 am

Re: Former VSS user, confused by differences

Post by Mordachai » Wed Nov 13, 2013 8:28 am

lbauer wrote:
The fact that the files are read-only should - by definition - mean that they can be overwritten by Vault without warning, without default options being considered at all. Just overwrite the files please (because they're read-only, meaning that they're not writable - they're not in edit mode - they're not checked out - they are fully available to be updated).
Vault is a replacement for VSS but isn't exactly like VSS because we've incorporated features which give users more options for development style.

For instance, Vault supports CVS mode (edit, merge, commit), where all files in the working folder are writable, and files don't need to be checked out before editing. The behavior described above wouldn't be applicable to those users.
Is Vault just better tooled to handle that model? Am I forcing a square peg into a round hold by trying to use it in a VSS interaction model?

Since the client offers VSS style (there is a configuration radio-button), can't it use that information to then be intelligent and better support that model?

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

Re: Former VSS user, confused by differences

Post by lbauer » Wed Nov 13, 2013 11:31 am

Since the client offers VSS style (there is a configuration radio-button), can't it use that information to then be intelligent and better support that model?
Good point.

We do have feature request 17472 logged for this functionality. We'll evaluate it for a future release of Vault.
Linda Bauer
SourceGear
Technical Support Manager

Mordachai
Posts: 84
Joined: Sun Feb 24, 2013 11:58 am

Re: Former VSS user, confused by differences

Post by Mordachai » Wed Nov 13, 2013 11:51 am

Awesome. I know that this would hugely impact my scripting & work flow in a positive manner.

B/R - Mordachai

Post Reply