Vault/Nant: could not map path to anything useful

[mayfield]

Hello all,

I'm setting up NAnt (v0.83) to check out our source code from Vault (v4.1.2) and during the <vaultget> task, I'm getting an error that says: "Could not map path to anything useful." I've been unable to find any hints via google or here in the support forums referencing this message, but I suspect it has something to do with not having the working folder set correctly. I AM able to use <vaultgettolocationoutsideworkingfolder> to successfully get the fles. My use of <vaultget> is based directly from the build sample (2) in the /examples/ folder of the Vault NAnt tasks library.

Anyone have any idea what I might be missing? I'm including the portion of my build script below that deals with the vault. Thanks in advance.

<target name="get" description="Grab the latest source code">
<!--Set login options: username, password, url, repository.-->
<vaultsetloginoptions
URL="http://*****************/VaultService"
user="**********" password="**********"
repository="*********" />
<!--Set a working folder.-->
<vaultsetworkingfolder repositoryFolderPath="$/***********/***********"
diskPath="c:\Program Files\NAnt\BuildScripts\**********\Web\Source\"
CreateDiskPath="true" />
<!--Do a get on the working folder.-->
<vaultget verbose="true">
<vaultfileset>
<include name="c:\Program Files\NAnt\BuildScripts\************\Web\Source\" />
</vaultfileset>
<getoptions Recursive="false" />
</vaultget>
</target>

[mayfield]

Seem to have solved this myself.

Turns out the direction of the slashes on the <vaultget> and <vaultsetworkingfolder> are sensitive as to whether or not you use \ or / characters. The examples from SourceGear use / slashes, but I had subconsienciously retyped my paths using \ slashes because that's the standar character used on the Windows file system. Turns out, the vault-related tasks really do care what slashes you use. This error message is not very clear, IMHO, but I was able to make it work.

[Beth]

Thanks for the update. Happy to hear it's working.