I'm trying to setting up the ProjFs environment in a VHD mapped drive that I created for this.
Everything went well, I set the --virtroot to @"X:\" (my vhd drive letter), and the folders in the first level appears as well when I opened my windows explorer.
But when I try to navigate to the second level of folders hierarchy, I mean, the second projected level, the Explorer thorws an error like this:
I wasn't be able to find any bug in the Managed-API, if it really exists or this is a "by design" limitation.
My solution requirements not allow me to create a sub folder and set the virtual root to it, cause the path would be changed.
I'm trying to setting up the ProjFs environment in a VHD mapped drive that I created for this.
Everything went well, I set the --virtroot to
@"X:\"(my vhd drive letter), and the folders in the first level appears as well when I opened my windows explorer.But when I try to navigate to the second level of folders hierarchy, I mean, the second projected level, the Explorer thorws an error like this:
I wasn't be able to find any bug in the Managed-API, if it really exists or this is a "by design" limitation.
My solution requirements not allow me to create a sub folder and set the virtual root to it, cause the path would be changed.