Can backslashes be used in Repository paths?

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

Moderator: SourceGear

Post Reply
jdavidi
Posts: 48
Joined: Thu Jul 06, 2006 1:29 pm

Can backslashes be used in Repository paths?

Post by jdavidi » Fri Jul 07, 2006 8:53 am

Greetings all!

We're in the middle of our Vault evalutation, and I just ran into a problem with a get in my build script. Here's my command line:

"C:\Program Files\SourceGear\Vault Client\vault.exe" -host engvault -user jdav -repository NewTest get $\8.0\8.01.maint\NetSource\Costguard\Applications\CustomerManagement -setfiletime current

I receive an invalid repository path error, but if I flip all the -repository param to $/8.0/8.01.maint/NetSource/Costguard/Applications/CustomerManagement

all is well.

While I'm pretty sure the use of forward slashes is more or less an industry standard for version control software, SourceSafe has accepted backslashes in project paths for all of its command line arguments.

Is there a setting I can flip somewhere to allow backslashes, or do I need to do some find/replace activity in my project path string before passing it to both Vault and the Windows Explorer?

Thanks!

--jdavidi

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

Post by Beth » Fri Jul 07, 2006 10:02 am

Currently we do not have an option to use back slashes instead of forward slashes. I can put in a feature request to support that in some future release.

Post Reply