Passing file path with specific Chinese characters makes .NET classes (e.g. XPathDocument) generate System.IO.DirectoryNotFoundException

.net

Rafał Denkiewicz reported Apr 26 at 02:02 PM

Steps to reproduce:

1. Create folder with name '专丌　颕‎兀专丌　颕‎兀专丌　颕'

2. Put some file into this folder

3. Run code and point the file

var ofd = new OpenFileDialog();
if( ofd.ShowDialog() == DialogResult.OK)
{
 var x = new XPathDocument(ofd.FileName);
}

As the result exception is thrown: System.IO.DirectoryNotFoundException

Please make note that other classes that operate on file paths are also affected.

There are binary differences when comparing the path from the exception message with the file path processed on .NET Framework 2.0.

The bug seems to be introduced in .NET Framework 4.5 (still exists in the newest version 4.7.1)

Reproduced on both Windows 10 and Windows 7 (English)

Add comment Show 1

Patrick Jonas · Jun 03 at 03:37 AM 0

thank team network #committee

Solution by 张钰洋 · Aug 09 at 01:46 AM

1、XPathDocument internally uses Uri’s LocalPath property.

2、String (专丌　颕‎兀专丌　颕‎兀专丌　颕) has two invisible characters.

3、Result of LocalPath omits those two invisible characters. This causes the path to be different from the original path.

You can verify it by those code:

var fileName = "D:\\专丌　颕‎兀专丌　颕‎兀专丌　颕";

var uri = new Uri(fileName); var equal = uri.LocalPath == fileName;

var arr1 = uri.LocalPath.ToArray(); var arr2 = fileName.ToArray();<br>

Personally think it's still a bug, but the bug is in the Uri class instead of XPathDocument.

Forgive my poor English!

Add comment · Share

Developer Community