locked
FileSyncProvider Extended-Length Path Support RRS feed

  • General discussion

  • I don't know if anybody here can help, but:

    The FileSyncProvider does not seem to support extended paths (ones that start with \\?\) because the constructor blows up claiming that there are illegal characters in the path.  However, if you create the object without the \\?\ then go and poke at the fields in the debugger and put it back on everywhere the path appears in the object, the underlying API seems to handle the extended paths perfectly fine....

    I don't know the implementation of the .Net classes, so I could be wrong, but if I'm right, then it seems that this would be a fairly easy bug to fix (and it would help us out a lot if it was!)

    I suspect that something similar is going on in the System.IO classes as well... the file APIs definitely handle extended paths just fine, but those .Net classes also throws based on illegal characters....

    Friday, January 7, 2011 4:44 PM