Path or file names too long

[joakimwg]

I'm using the Vault CLI client to pull out all C and H files from our repository to a server making them searchable for everyone.

Previously we used the shadow folder for this, but that started failing because of the path depth. Moving to the CLI client solved the problem for a while. Think this in some way got used a bit shorter paths, and therefor getting around the DotNET path issue.

Not I'm experiencing the same issue using the CLI client as well. Are there any plans on having this issue addressed. A path depth of 248 (or 260) isn't that deep and a repository can easily get that path depth.

[Beth]

I can put in a feature request for longer path names. We follow the Windows default for path length. I'm not sure if a change is feasible. Some articles seem to suggest issues with forcing longer path names in Windows, and even if there were changes in newer versions of Windows, we still support some older versions.

One thing that might help is to have multiple shadow folders for the sub-folders instead of having just one set at a higher level. For example, if you have a tree that looks like:

$
---- Project 1
---- Project 2
---- Project 3

Instead of setting the shadow folder to shadow $, you could create 3 shadow folders. You'd have a shadow folder for Project 1, and a separate one for Project 2 and so on.

F: 17492

[joakimwg]

Using multiple shadow folders is an interim solution, but it's not a long term solution. As new projects are arred we have to manually go in an add them as new shadow folders.