IExplorerUtil.GetWorkingFolder() returns wrong path?

[Anonymous]

As subject. When I pass the serviceManager.DocumentService.GetFolderRoot() I get "C:\\Users\\noontz\\Documents\\Vault\\" instead of the correct mapping  "C:\\vaultroot\\" ( in this case )..

Here´s my usual suspects:

 I´m using Vault Basic, BUT, ExplorerLoader.LoadExplorerUtil() returns a IExplorerUtil just fine, so I presume the limitations is on explorer extensions?

 The local folder is not yet created, BUT, Opening the explorer > add file ( Anywhere on the computer/myFile.txt ) > get/checkout will create the rootfolder correctly e.g. "C:\\vaultroot\\myFile.txt", so the correct information is there somewhere.

Bottom line: How do I obtain the correct local mirror of  "$" with vault basic through API

[Redmond.D]

How is the working folder set in your Vault?  Is it through the "Enforce Working Folder" option in the Vault settings?

[Anonymous]

In both my test cases yes.

That said I´m looking for a solution that works in both scenarios ( enforce OR allow )

Since the information is persistent some kind of hack should be possible, but despite half a days search in the registry and a vast amount of XML like files for something interesting: No cigar 😞

[Redmond.D · Accepted solution]

Try this algorithm....

Use the DocumentService to read the setting "enforce" setting from the Vault server.

GetEnforceWorkingFolder() tells you if the feature has been enabled.  If it returns true, use GetRequiredWorkingFolderLocation() to find the Value.

If false, use IExplorerUtil.GetWorkingFolder().

[Anonymous]

That did it! ( both scenarios & vault basic ) Big thanks Doug! You just saved my day ( and the next three or four I believe  )  This also answers my last post in this thread about a less heavy way to get the local root path.

I´m a happy man! ( Where is that smiley with two beers ? )