fix: MockFileSystem's File.WriteAllText, File.ReadAllText, Directory.GetFiles, Directory.Create fail with \\?\C:\foo style paths

[mostynb]

This is an attempt to fix #1304.

[vbreuss]

@mostynb : Thanks for the PR. Could you please check the failing actions?

What happens on the real file system when you use Directory.GetFiles when the directory is prefixed with \\?\? Are the returned strings also prefixed with \\?\?

[mostynb]

Pushed an update which added braces to the if block, and updated the PR title.

What happens on the real file system when you use Directory.GetFiles when the directory is prefixed with \?? Are the returned strings also prefixed with \??

If I give System.IO.Directory.GetFiles() a \?\ style path on windows, it returns \?\ style paths.

[vbreuss]

@mostynb

If I give System.IO.Directory.GetFiles() a \\?\ style path on windows, it returns \\?\ style paths.

But this does not work on the MockFileSystem, even after this pull request, right?

[mostynb]

@mostynb

If I give System.IO.Directory.GetFiles() a \\?\ style path on windows, it returns \\?\ style paths.

But this does not work on the MockFileSystem, even after this pull request, right?

It did not, so I pushed some changes to make it work, assuming that you always use \\?\ style paths.

However, extended length paths aren't normalised internally in MockFileSystem. eg if I create \\?\C:\foo\bar.txt then I can read \\?\C:\foo\bar.txt, but C:\foo\bar.txt does not appear to exist.

[vbreuss]

Thanks @mostynb, will publish v22.0.15 shortly!

[github-actions]

This is addressed in release v22.0.15.