Due to the fact that the convertToUnixPath function turns double slash or backslash into single, UNC paths like \foo\bar will be corrupted by any functions that use convertToUnixPath. This is called in a lots of places, including directoryInfoList, where it caused me problems.
I have the feeling that convertToUnixPath probably shouldn't be called so much on Windows. convertToWindowsPath has the same problem, by the looks of it, though.
A workaround is to remove the lines that do the slash-reduction, since really, that's not very necessary anyway. The OS will deal with it.
Due to the fact that the convertToUnixPath function turns double slash or backslash into single, UNC paths like \foo\bar will be corrupted by any functions that use convertToUnixPath. This is called in a lots of places, including directoryInfoList, where it caused me problems.
I have the feeling that convertToUnixPath probably shouldn't be called so much on Windows. convertToWindowsPath has the same problem, by the looks of it, though.
A workaround is to remove the lines that do the slash-reduction, since really, that's not very necessary anyway. The OS will deal with it.