[CLI] "libman cache clean <provider>" command results in funky file paths in error message when file is locked

[aspnet]

[CLI] "libman cache clean " command results in funky file paths in error message when file is locked

from librarymanager.

[jimmylewis]

I don't think we can do much here. We try to delete the directory, and that's locked because of the open handle on the file. We don't know which file it is, and looking up open handles on a given file (e.g. if we iterated all the files) is non-trivial on Windows (it needs custom drivers, UAC, security, oh my!), and not applicable on other OS (since they typically don't hold locks on files).

As for the path format, that's coming from the inner exception, possibly a .NET Core behavior. I don't think it's worth messing with that either (doesn't seem worth the effort).