blocks|key|1441530|text|只要做就行了；|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1441531|System.IO.FileInfo+fi+=+null;
try+{
++fi+=+new+System.IO.FileInfo(fileName);
}
catch+(ArgumentException)+{+}
catch+(System.IO.PathTooLongException)+{+}
catch+(NotSupportedException)+{+}
if+(ReferenceEquals(fi,+null))+{
++//+file+name+is+not+valid
}+else+{
++//+file+name+is+valid...+May+check+for+existence+by+calling+fi.Exists.
}|code-block|syntax|javascript|1441532|创建FileInfo实例时，该文件不需要存在。|offset|length|style|CODE|1441533|entityMap^0|0|0|2|8|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Just do;

<pre><code>System.IO.FileInfo fi = null;
try {
 fi = new System.IO.FileInfo(fileName);
}
catch (ArgumentException) { }
catch (System.IO.PathTooLongException) { }
catch (NotSupportedException) { }
if (ReferenceEquals(fi, null)) {
 // file name is not valid
} else {
 // file name is valid... May check for existence by calling fi.Exists.
}
</code></pre>

For creating a <code>FileInfo</code> instance the file does not need to exist.

blocks|key|1656112|text|您可以从Path.GetInvalidPathChars和GetInvalidFileNameChars中获取无效字符的列表，如this+question中所述。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1656113|正如jberger所指出的，此方法的响应中没有包括一些其他字符。有关windows平台的更多细节，请查看MSDN上的Naming+Files,+Paths+and+Namespaces。|1656114|作为Micah+points+out，可以使用Directory.GetLogicalDrives获取有效驱动器的列表。|1656115|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.microsoft.com/en-us/dotnet/api/system.io.path.getinvalidpathchars|1|https://docs.microsoft.com/en-us/dotnet/api/system.io.path.getinvalidfilenamechars|2|https://stackoverflow.com/questions/62771/how-check-if-given-string-is-legal-allowed-file-name-under-windows|3|https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file|4|https://stackoverflow.com/questions/422090/in-c-check-that-filename-is-possibly-valid-not-that-it-exists#422131|5|https://docs.microsoft.com/en-us/dotnet/api/system.io.directory.getlogicaldrives^0|4|O|T|N|4|O|0|T|N|1|1S|D|2|0|1M|Y|3|0|N|Q|8|A|4|N|Q|5|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@$9|16|A|17|1|18]|$9|19|A|1A|1|1B]|$9|1C|A|1D|1|1E]]|E|$]]|$1|F|3|G|5|6|7|1F|8|@]|D|@$9|1G|A|1H|1|1I]]|E|$]]|$1|H|3|I|5|6|7|1J|8|@$9|1K|A|1L|B|C]]|D|@$9|1M|A|1N|1|1O]|$9|1P|A|1Q|1|1R]]|E|$]]|$1|J|3|-4|5|6|7|1S|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]|R|$5|M|N|O|E|$P|S]]|T|$5|M|N|O|E|$P|U]]|V|$5|M|N|O|E|$P|W]]|X|$5|M|N|O|E|$P|Y]]|Z|$5|M|N|O|E|$P|10]]]]

You can get a list of invalid characters from <a href="https://docs.microsoft.com/en-us/dotnet/api/system.io.path.getinvalidpathchars" rel="nofollow noreferrer"><code>Path.GetInvalidPathChars</code></a> and <a href="https://docs.microsoft.com/en-us/dotnet/api/system.io.path.getinvalidfilenamechars" rel="nofollow noreferrer"><code>GetInvalidFileNameChars</code></a> as discussed in <a href="https://stackoverflow.com/questions/62771/how-check-if-given-string-is-legal-allowed-file-name-under-windows">this question</a>.
As noted by jberger, there some other characters which are not included in the response from this method. For much more details of the windows platform, take a look at <a href="https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file" rel="nofollow noreferrer">Naming Files, Paths and Namespaces</a> on MSDN.
As Micah <a href="https://stackoverflow.com/questions/422090/in-c-check-that-filename-is-possibly-valid-not-that-it-exists#422131">points out</a>, there is <a href="https://docs.microsoft.com/en-us/dotnet/api/system.io.directory.getlogicaldrives" rel="nofollow noreferrer"><code>Directory.GetLogicalDrives</code></a> to get a list of valid drives.

blocks|key|1441855|text|您可以使用System.Uri类。Uri类不仅对web+URL有用，它还可以处理文件系统路径。使用Uri.TryCreate方法查找路径是否为根路径，然后使用IsLoopback属性确定Uri是否引用本地计算机。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1441856|下面是一个简单的方法，它可以确定一个字符串是否是有效的本地根文件路径。|1441857|public+bool+IsPathValidRootedLocal(String+pathString)+{
++++Uri+pathUri;
++++Boolean+isValidUri+=+Uri.TryCreate(pathString,+UriKind.Absolute,+out+pathUri);
++++return+isValidUri+&&+pathUri+!=+null+&&+pathUri.IsLoopback;
}|code-block|syntax|javascript|1441858|我相信这将会奏效。|1441859|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

You could make use the System.Uri class. The Uri class isn't just useful for web URLs, it also handles file system paths as well. Use the Uri.TryCreate method to find if the path is rooted then use the IsLoopback property to determine if the Uri references the local machine.

Here is a simple method which determines if a string is a valid, local, and rooted file path.

<pre><code>public bool IsPathValidRootedLocal(String pathString) {
 Uri pathUri;
 Boolean isValidUri = Uri.TryCreate(pathString, UriKind.Absolute, out pathUri);
 return isValidUri &amp;&amp; pathUri != null &amp;&amp; pathUri.IsLoopback;
}
</code></pre>

I am confident this will work.

blocks|key|1656404|text|您可以使用System.IO名称空间中存在的几种方法：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1656405|Directory.GetLogicalDrives()+//+Returns+an+array+of+strings+like+"c:\"
Path.GetInvalidFileNameChars()+//+Returns+an+array+of+characters+that+cannot+be+used+in+a+file+name
Path.GetInvalidPathChars()+//+Returns+an+array+of+characters+that+cannot+be+used+in+a+path.|code-block|syntax|javascript|1656406|按照建议，您可以执行以下操作：|1656407|bool+IsValidFilename(string+testName)+{
++++string+regexString+=+"["+%2B+Regex.Escape(Path.GetInvalidPathChars())+%2B+"]";
++++Regex+containsABadCharacter+=+new+Regex(regexString);
++++if+(containsABadCharacter.IsMatch(testName))+{
++++++++return+false;
++++}

++++//+Check+for+drive
++++string+pathRoot+=+Path.GetPathRoot(testName);
++++if+(Directory.GetLogicalDrives().Contains(pathRoot))+{
++++++++//+etc
++++}

++++//+other+checks+for+UNC,+drive-path+format,+etc

++++return+true;
}|1656408|entityMap^0|5|9|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|P|$]]

There are several methods you could use that exist in the <code>System.IO</code> namespace:

<pre><code>Directory.GetLogicalDrives() // Returns an array of strings like "c:\"
Path.GetInvalidFileNameChars() // Returns an array of characters that cannot be used in a file name
Path.GetInvalidPathChars() // Returns an array of characters that cannot be used in a path.
</code></pre>

As suggested you could then do this:

<pre><code>bool IsValidFilename(string testName) {
 string regexString = "[" + Regex.Escape(Path.GetInvalidPathChars()) + "]";
 Regex containsABadCharacter = new Regex(regexString);
 if (containsABadCharacter.IsMatch(testName)) {
 return false;
 }

 // Check for drive
 string pathRoot = Path.GetPathRoot(testName);
 if (Directory.GetLogicalDrives().Contains(pathRoot)) {
 // etc
 }

 // other checks for UNC, drive-path format, etc

 return true;
}
</code></pre>

blocks|key|1441979|text|我想我会发布一个解决方案，我是从寻找同一问题的可靠解决方案后发现的一些答案拼凑而成的。希望它能帮助其他人。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1441980|using+System;
using+System.IO;
//..

public+static+bool+ValidateFilePath(string+path,+bool+RequireDirectory,+bool+IncludeFileName,+bool+RequireFileName+=+false)
{
++++if+(string.IsNullOrEmpty(path))+{+return+false;+}
++++string+root+=+null;
++++string+directory+=+null;
++++string+filename+=+null;
++++try
++++{
++++++++//+throw+ArgumentException+-+The+path+parameter+contains+invalid+characters,+is+empty,+or+contains+only+white+spaces.
++++++++root+=+Path.GetPathRoot(path);

++++++++//+throw+ArgumentException+-+path+contains+one+or+more+of+the+invalid+characters+defined+in+GetInvalidPathChars.
++++++++//+-or-+String.Empty+was+passed+to+path.
++++++++directory+=+Path.GetDirectoryName(path);

++++++++//+path+contains+one+or+more+of+the+invalid+characters+defined+in+GetInvalidPathChars
++++++++if+(IncludeFileName)+{+filename+=+Path.GetFileName(path);+}
++++}
++++catch+(ArgumentException)
++++{
++++++++return+false;
++++}

++++//+null+if+path+is+null,+or+an+empty+string+if+path+does+not+contain+root+directory+information
++++if+(String.IsNullOrEmpty(root))+{+return+false;+}

++++//+null+if+path+denotes+a+root+directory+or+is+null.+Returns+String.Empty+if+path+does+not+contain+directory+information
++++if+(String.IsNullOrEmpty(directory))+{+return+false;+}

++++if+(RequireFileName)
++++{
++++++++//+if+the+last+character+of+path+is+a+directory+or+volume+separator+character,+this+method+returns+String.Empty
++++++++if+(String.IsNullOrEmpty(filename))+{+return+false;+}

++++++++//+check+for+illegal+chars+in+filename
++++++++if+(filename.IndexOfAny(Path.GetInvalidFileNameChars())+>=+0)+{+return+false;+}
++++}
++++return+true;
}|code-block|syntax|javascript|1441981|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Thought I would post a solution I cobbled together from bits of answers I found after searching for a robust solution to the same problem. Hopefully it helps someone else.

<pre><code>using System;
using System.IO;
//..

public static bool ValidateFilePath(string path, bool RequireDirectory, bool IncludeFileName, bool RequireFileName = false)
{
 if (string.IsNullOrEmpty(path)) { return false; }
 string root = null;
 string directory = null;
 string filename = null;
 try
 {
 // throw ArgumentException - The path parameter contains invalid characters, is empty, or contains only white spaces.
 root = Path.GetPathRoot(path);

 // throw ArgumentException - path contains one or more of the invalid characters defined in GetInvalidPathChars.
 // -or- String.Empty was passed to path.
 directory = Path.GetDirectoryName(path);

 // path contains one or more of the invalid characters defined in GetInvalidPathChars
 if (IncludeFileName) { filename = Path.GetFileName(path); }
 }
 catch (ArgumentException)
 {
 return false;
 }

 // null if path is null, or an empty string if path does not contain root directory information
 if (String.IsNullOrEmpty(root)) { return false; }

 // null if path denotes a root directory or is null. Returns String.Empty if path does not contain directory information
 if (String.IsNullOrEmpty(directory)) { return false; }

 if (RequireFileName)
 {
 // if the last character of path is a directory or volume separator character, this method returns String.Empty
 if (String.IsNullOrEmpty(filename)) { return false; }

 // check for illegal chars in filename
 if (filename.IndexOfAny(Path.GetInvalidFileNameChars()) &gt;= 0) { return false; }
 }
 return true;
}
</code></pre>

blocks|key|1441616|text|即使文件名有效，您可能仍然希望对其执行touch操作，以确保用户具有写入权限。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1441617|如果你不想在短时间内处理数以百计的文件，我认为创建一个空文件是一个合理的方法。|1441618|如果你真的想要一些轻量级的东西，比如检查无效的字符，那么将你的文件名与Path.GetInvalidFileNameChars()进行比较。|1441619|entityMap^0|J|5|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|P|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|K|$]]

Even if the filename is valid, you may still want to <code>touch</code> it to be sure the user has permission to write.

If you won't be thrashing the disk with hundreds of files in a short period of time, I think creating an empty file is a reasonable approach.

If you really want something lighter, like just checking for invalid chars, then compare your filename against Path.GetInvalidFileNameChars().

blocks|key|1441571|text|使用System.IO+namespace中Path+class上的静态GetInvalidFileNameChars+method来确定文件名中的非法字符。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1441572|要在路径中执行此操作，请在同一个类上调用静态GetInvalidPathChars+method。|1441573|要确定路径的根是否有效，您可以调用Path类上的静态GetPathRoot+method来获取根，然后使用Directory+class来确定它是否有效。然后，您可以正常验证路径的其余部分。|1441574|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/29kt2zfk.aspx|1|http://msdn.microsoft.com/en-us/library/system.io.path.aspx|2|http://msdn.microsoft.com/en-us/library/system.io.path.getinvalidfilenamechars.aspx|3|http://msdn.microsoft.com/en-us/library/system.io.path.getinvalidpathchars.aspx|4|http://msdn.microsoft.com/en-us/library/system.io.path.getpathroot.aspx|5|http://msdn.microsoft.com/en-us/library/system.io.directory.aspx^0|2|9|M|4|10|N|2|J|0|M|A|1|10|U|2|0|M|J|M|Q|3|0|H|4|Q|B|1H|9|Q|I|4|1H|F|5|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]|$9|16|A|17|B|C]]|D|@$9|18|A|19|1|1A]|$9|1B|A|1C|1|1D]|$9|1E|A|1F|1|1G]]|E|$]]|$1|F|3|G|5|6|7|1H|8|@$9|1I|A|1J|B|C]]|D|@$9|1K|A|1L|1|1M]]|E|$]]|$1|H|3|I|5|6|7|1N|8|@$9|1O|A|1P|B|C]|$9|1Q|A|1R|B|C]|$9|1S|A|1T|B|C]]|D|@$9|1U|A|1V|1|1W]|$9|1X|A|1Y|1|1Z]]|E|$]]|$1|J|3|-4|5|6|7|20|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]|R|$5|M|N|O|E|$P|S]]|T|$5|M|N|O|E|$P|U]]|V|$5|M|N|O|E|$P|W]]|X|$5|M|N|O|E|$P|Y]]|Z|$5|M|N|O|E|$P|10]]]]

Use the static <a href="http://msdn.microsoft.com/en-us/library/system.io.path.getinvalidfilenamechars.aspx" rel="nofollow noreferrer"><code>GetInvalidFileNameChars</code> method</a> on the <a href="http://msdn.microsoft.com/en-us/library/system.io.path.aspx" rel="nofollow noreferrer"><code>Path</code> class</a> in the <a href="http://msdn.microsoft.com/en-us/library/29kt2zfk.aspx" rel="nofollow noreferrer"><code>System.IO</code> namespace</a> to determine what characters are illegal in a file name.

To do so in a path, call the static <a href="http://msdn.microsoft.com/en-us/library/system.io.path.getinvalidpathchars.aspx" rel="nofollow noreferrer"><code>GetInvalidPathChars</code> method</a> on the same class.

To determine if the root of a path is valid, you would call the static <a href="http://msdn.microsoft.com/en-us/library/system.io.path.getpathroot.aspx" rel="nofollow noreferrer"><code>GetPathRoot</code> method</a> on the <code>Path</code> class to get the root, then use the <a href="http://msdn.microsoft.com/en-us/library/system.io.directory.aspx" rel="nofollow noreferrer"><code>Directory</code> class</a> to determine if it is valid. Then you can validate the rest of the path normally.

blocks|key|1442040|text|尝试这个方法，它将尝试覆盖所有可能的异常情况。它几乎适用于所有与Windows相关的路径。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1442041|///+<summary>
///+Validate+the+Path.+If+path+is+relative+append+the+path+to+the+project+directory+by+default.
///+</summary>
///+<param+name="path">Path+to+validate</param>
///+<param+name="RelativePath">Relative+path</param>
///+<param+name="Extension">If+want+to+check+for+File+Path</param>
///+<returns></returns>
private+static+bool+ValidateDllPath(ref+string+path,+string+RelativePath+=+"",+string+Extension+=+"")+{
++++//+Check+if+it+contains+any+Invalid+Characters.
++++if+(path.IndexOfAny(Path.GetInvalidPathChars())+==+-1)+{
++++++++try+{
++++++++++++//+If+path+is+relative+take+%25IGXLROOT%25+as+the+base+directory
++++++++++++if+(!Path.IsPathRooted(path))+{
++++++++++++++++if+(string.IsNullOrEmpty(RelativePath))+{
++++++++++++++++++++//+Exceptions+handled+by+Path.GetFullPath
++++++++++++++++++++//+ArgumentException+path+is+a+zero-length+string,+contains+only+white+space,+or+contains+one+or+more+of+the+invalid+characters+defined+in+GetInvalidPathChars.+-or-+The+system+could+not+retrieve+the+absolute+path.
++++++++++++++++++++//+
++++++++++++++++++++//+SecurityException+The+caller+does+not+have+the+required+permissions.
++++++++++++++++++++//+
++++++++++++++++++++//+ArgumentNullException+path+is+null.
++++++++++++++++++++//+
++++++++++++++++++++//+NotSupportedException+path+contains+a+colon+(":")+that+is+not+part+of+a+volume+identifier+(for+example,+"c:\").+
++++++++++++++++++++//+PathTooLongException+The+specified+path,+file+name,+or+both+exceed+the+system-defined+maximum+length.+For+example,+on+Windows-based+platforms,+paths+must+be+less+than+248+characters,+and+file+names+must+be+less+than+260+characters.

++++++++++++++++++++//+RelativePath+is+not+passed+so+we+would+take+the+project+path+
++++++++++++++++++++path+=+Path.GetFullPath(RelativePath);

++++++++++++++++}+else+{
++++++++++++++++++++//+Make+sure+the+path+is+relative+to+the+RelativePath+and+not+our+project+directory
++++++++++++++++++++path+=+Path.Combine(RelativePath,+path);
++++++++++++++++}
++++++++++++}

++++++++++++//+Exceptions+from+FileInfo+Constructor:
++++++++++++//+++System.ArgumentNullException:
++++++++++++//+++++fileName+is+null.
++++++++++++//
++++++++++++//+++System.Security.SecurityException:
++++++++++++//+++++The+caller+does+not+have+the+required+permission.
++++++++++++//
++++++++++++//+++System.ArgumentException:
++++++++++++//+++++The+file+name+is+empty,+contains+only+white+spaces,+or+contains+invalid+characters.
++++++++++++//
++++++++++++//+++System.IO.PathTooLongException:
++++++++++++//+++++The+specified+path,+file+name,+or+both+exceed+the+system-defined+maximum
++++++++++++//+++++length.+For+example,+on+Windows-based+platforms,+paths+must+be+less+than
++++++++++++//+++++248+characters,+and+file+names+must+be+less+than+260+characters.
++++++++++++//
++++++++++++//+++System.NotSupportedException:
++++++++++++//+++++fileName+contains+a+colon+(:)+in+the+middle+of+the+string.
++++++++++++FileInfo+fileInfo+=+new+FileInfo(path);

++++++++++++//+Exceptions+using+FileInfo.Length:
++++++++++++//+++System.IO.IOException:
++++++++++++//+++++System.IO.FileSystemInfo.Refresh()+cannot+update+the+state+of+the+file+or
++++++++++++//+++++directory.
++++++++++++//
++++++++++++//+++System.IO.FileNotFoundException:
++++++++++++//+++++The+file+does+not+exist.-or-+The+Length+property+is+called+for+a+directory.
++++++++++++bool+throwEx+=+fileInfo.Length+==+-1;

++++++++++++//+Exceptions+using+FileInfo.IsReadOnly:
++++++++++++//+++System.UnauthorizedAccessException:
++++++++++++//+++++Access+to+fileName+is+denied.
++++++++++++//+++++The+file+described+by+the+current+System.IO.FileInfo+object+is+read-only.-or-
++++++++++++//+++++This+operation+is+not+supported+on+the+current+platform.-or-+The+caller+does
++++++++++++//+++++not+have+the+required+permission.
++++++++++++throwEx+=+fileInfo.IsReadOnly;

++++++++++++if+(!string.IsNullOrEmpty(Extension))+{
++++++++++++++++//+Validate+the+Extension+of+the+file.
++++++++++++++++if+(Path.GetExtension(path).Equals(Extension,+StringComparison.InvariantCultureIgnoreCase))+{
++++++++++++++++++++//+Trim+the+Library+Path
++++++++++++++++++++path+=+path.Trim();
++++++++++++++++++++return+true;
++++++++++++++++}+else+{
++++++++++++++++++++return+false;
++++++++++++++++}
++++++++++++}+else+{
++++++++++++++++return+true;

++++++++++++}
++++++++}+catch+(ArgumentNullException)+{
++++++++++++//+++System.ArgumentNullException:
++++++++++++//+++++fileName+is+null.
++++++++}+catch+(System.Security.SecurityException)+{
++++++++++++//+++System.Security.SecurityException:
++++++++++++//+++++The+caller+does+not+have+the+required+permission.
++++++++}+catch+(ArgumentException)+{
++++++++++++//+++System.ArgumentException:
++++++++++++//+++++The+file+name+is+empty,+contains+only+white+spaces,+or+contains+invalid+characters.
++++++++}+catch+(UnauthorizedAccessException)+{
++++++++++++//+++System.UnauthorizedAccessException:
++++++++++++//+++++Access+to+fileName+is+denied.
++++++++}+catch+(PathTooLongException)+{
++++++++++++//+++System.IO.PathTooLongException:
++++++++++++//+++++The+specified+path,+file+name,+or+both+exceed+the+system-defined+maximum
++++++++++++//+++++length.+For+example,+on+Windows-based+platforms,+paths+must+be+less+than
++++++++++++//+++++248+characters,+and+file+names+must+be+less+than+260+characters.
++++++++}+catch+(NotSupportedException)+{
++++++++++++//+++System.NotSupportedException:
++++++++++++//+++++fileName+contains+a+colon+(:)+in+the+middle+of+the+string.
++++++++}+catch+(FileNotFoundException)+{
++++++++++++//+System.FileNotFoundException
++++++++++++//++The+exception+that+is+thrown+when+an+attempt+to+access+a+file+that+does+not
++++++++++++//++exist+on+disk+fails.
++++++++}+catch+(IOException)+{
++++++++++++//+++System.IO.IOException:
++++++++++++//+++++An+I/O+error+occurred+while+opening+the+file.
++++++++}+catch+(Exception)+{
++++++++++++//+Unknown+Exception.+Might+be+due+to+wrong+case+or+nulll+checks.
++++++++}
++++}+else+{
++++++++//+Path+contains+invalid+characters
++++}
++++return+false;
}|code-block|syntax|javascript|1442042|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Try out this method which would try to cover for all the possible Exceptions scenarios. It would work for almost all the Windows related Paths.

<pre><code>/// &lt;summary&gt;
/// Validate the Path. If path is relative append the path to the project directory by default.
/// &lt;/summary&gt;
/// &lt;param name="path"&gt;Path to validate&lt;/param&gt;
/// &lt;param name="RelativePath"&gt;Relative path&lt;/param&gt;
/// &lt;param name="Extension"&gt;If want to check for File Path&lt;/param&gt;
/// &lt;returns&gt;&lt;/returns&gt;
private static bool ValidateDllPath(ref string path, string RelativePath = "", string Extension = "") {
 // Check if it contains any Invalid Characters.
 if (path.IndexOfAny(Path.GetInvalidPathChars()) == -1) {
 try {
 // If path is relative take %IGXLROOT% as the base directory
 if (!Path.IsPathRooted(path)) {
 if (string.IsNullOrEmpty(RelativePath)) {
 // Exceptions handled by Path.GetFullPath
 // ArgumentException path is a zero-length string, contains only white space, or contains one or more of the invalid characters defined in GetInvalidPathChars. -or- The system could not retrieve the absolute path.
 // 
 // SecurityException The caller does not have the required permissions.
 // 
 // ArgumentNullException path is null.
 // 
 // NotSupportedException path contains a colon (":") that is not part of a volume identifier (for example, "c:\"). 
 // PathTooLongException The specified path, file name, or both exceed the system-defined maximum length. For example, on Windows-based platforms, paths must be less than 248 characters, and file names must be less than 260 characters.

 // RelativePath is not passed so we would take the project path 
 path = Path.GetFullPath(RelativePath);

 } else {
 // Make sure the path is relative to the RelativePath and not our project directory
 path = Path.Combine(RelativePath, path);
 }
 }

 // Exceptions from FileInfo Constructor:
 // System.ArgumentNullException:
 // fileName is null.
 //
 // System.Security.SecurityException:
 // The caller does not have the required permission.
 //
 // System.ArgumentException:
 // The file name is empty, contains only white spaces, or contains invalid characters.
 //
 // System.IO.PathTooLongException:
 // The specified path, file name, or both exceed the system-defined maximum
 // length. For example, on Windows-based platforms, paths must be less than
 // 248 characters, and file names must be less than 260 characters.
 //
 // System.NotSupportedException:
 // fileName contains a colon (:) in the middle of the string.
 FileInfo fileInfo = new FileInfo(path);

 // Exceptions using FileInfo.Length:
 // System.IO.IOException:
 // System.IO.FileSystemInfo.Refresh() cannot update the state of the file or
 // directory.
 //
 // System.IO.FileNotFoundException:
 // The file does not exist.-or- The Length property is called for a directory.
 bool throwEx = fileInfo.Length == -1;

 // Exceptions using FileInfo.IsReadOnly:
 // System.UnauthorizedAccessException:
 // Access to fileName is denied.
 // The file described by the current System.IO.FileInfo object is read-only.-or-
 // This operation is not supported on the current platform.-or- The caller does
 // not have the required permission.
 throwEx = fileInfo.IsReadOnly;

 if (!string.IsNullOrEmpty(Extension)) {
 // Validate the Extension of the file.
 if (Path.GetExtension(path).Equals(Extension, StringComparison.InvariantCultureIgnoreCase)) {
 // Trim the Library Path
 path = path.Trim();
 return true;
 } else {
 return false;
 }
 } else {
 return true;

 }
 } catch (ArgumentNullException) {
 // System.ArgumentNullException:
 // fileName is null.
 } catch (System.Security.SecurityException) {
 // System.Security.SecurityException:
 // The caller does not have the required permission.
 } catch (ArgumentException) {
 // System.ArgumentException:
 // The file name is empty, contains only white spaces, or contains invalid characters.
 } catch (UnauthorizedAccessException) {
 // System.UnauthorizedAccessException:
 // Access to fileName is denied.
 } catch (PathTooLongException) {
 // System.IO.PathTooLongException:
 // The specified path, file name, or both exceed the system-defined maximum
 // length. For example, on Windows-based platforms, paths must be less than
 // 248 characters, and file names must be less than 260 characters.
 } catch (NotSupportedException) {
 // System.NotSupportedException:
 // fileName contains a colon (:) in the middle of the string.
 } catch (FileNotFoundException) {
 // System.FileNotFoundException
 // The exception that is thrown when an attempt to access a file that does not
 // exist on disk fails.
 } catch (IOException) {
 // System.IO.IOException:
 // An I/O error occurred while opening the file.
 } catch (Exception) {
 // Unknown Exception. Might be due to wrong case or nulll checks.
 }
 } else {
 // Path contains invalid characters
 }
 return false;
}
</code></pre>

blocks|key|1441673|text|我不知道有什么开箱即用的方法可以为您验证所有这些，但是.NET中的Path类可以为您提供极大的帮助。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1441674|首先，它有：|1441675|char[]+invalidChars+=+Path.GetInvalidFileNameChars();+//returns+invalid+charachters|code-block|syntax|javascript|1441676|或者：|1441677|Path.GetPathRoot(string);+//+will+return+the+root.|1441678|entityMap^0|R|4|X|4|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|Q|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|R|$]]

I don't know of anything out of the box that can just validate all of that for you, however the <code>Path</code> class in <code>.NET</code> can help you out tremendously. 

For starters, it has:

<pre><code>char[] invalidChars = Path.GetInvalidFileNameChars(); //returns invalid charachters
</code></pre>

or:

<pre><code>Path.GetPathRoot(string); // will return the root.
</code></pre>

blocks|key|1441804|text|正如其他人所展示的那样，我很幸运地使用了正则表达式。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1441805|要记住的一件事是，Windows至少禁止一些包含合法字符的文件名。我想到了几个:+com，nul，prn。|1441806|我现在没有它，但是我有一个正则表达式，它将这些文件名考虑在内。如果你愿意，我可以把它贴出来，否则我相信你可以像我一样找到它:谷歌。|1441807|-Jay|1441808|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I've had luck using regular expressions as others have shown.

One thing to keep in mind is that Windows at least prohibits some filenames that otherwise containlegal characters. A few come to mind: com, nul, prn.

I don't have it with me now, but I have a regex that takes these filename into consideration. If you want I can post it, otherwise I'm sure you can find it the same way I did: Google.

-Jay

blocks|key|1441644|text|可能最好的方法是构建一个自定义方法，混合使用正则表达式和文件系统上的小查找(例如，查看驱动器)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1441645|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Probably the bast way is to build a custom method mixing a combination of regex and small look up on your file system (to see the drives, for example)

blocks|key|1441749|text|这将使您获得机器上的驱动器：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1441750|System.IO.DriveInfo.GetDrives()|code-block|syntax|javascript|1441751|这两种方法将让您检查错误的字符：|1441752|System.IO.Path.GetInvalidFileNameChars();
System.IO.Path.GetInvalidPathChars();|1441753|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

This will get you the drives on the machine:

<pre><code>System.IO.DriveInfo.GetDrives()
</code></pre>

These two methods will get you the bad characters to check:

<pre><code>System.IO.Path.GetInvalidFileNameChars();
System.IO.Path.GetInvalidPathChars();
</code></pre>

blocks|key|1441927|text|我觉得现在回答已经太晚了，但是...:)如果路径是卷名，可以这样写：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1441928|using+System;
using+System.Linq;
using+System.IO;

//+...

var+drives+=+Environment.GetLogicalDrives();
var+invalidChars+=+Regex.Replace(new+string(Path.GetInvalidFileNameChars()),+"[\\\\/]",+"");
var+drive+=+drives.FirstOrDefault(d+=>+filePath.StartsWith(d));
if+(drive+!=+null)+{
++++var+fileDirPath+=+filePath.Substring(drive.Length);
++++if+(0+<+fileDirPath.Length)+{
++++++++if+(fileDirPath.IndexOfAny(invalidChars.ToCharArray())+==+-1)+{
++++++++++++if+(Path.Combine(drive,+fileDirPath)+!=+drive)+{
++++++++++++++++//+path+correct+and+we+can+proceed
++++++++++++}
++++++++}
++++}
}|code-block|syntax|javascript|1441929|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Think it's too late to answer but... :)
in case of path with volume name you could write something like this:

<pre><code>using System;
using System.Linq;
using System.IO;

// ...

var drives = Environment.GetLogicalDrives();
var invalidChars = Regex.Replace(new string(Path.GetInvalidFileNameChars()), "[\\\\/]", "");
var drive = drives.FirstOrDefault(d =&gt; filePath.StartsWith(d));
if (drive != null) {
 var fileDirPath = filePath.Substring(drive.Length);
 if (0 &lt; fileDirPath.Length) {
 if (fileDirPath.IndexOfAny(invalidChars.ToCharArray()) == -1) {
 if (Path.Combine(drive, fileDirPath) != drive) {
 // path correct and we can proceed
 }
 }
 }
}
</code></pre>

Is there a method in the System.IO namespace that checks the validity of a filename?

For example, <code>C:\foo\bar</code> would validate and <code>:"~-*</code> would not

Or a little trickier, <code>X:\foo\bar</code> would validate is there is an <code>X:</code> drive on the system, but wouldn't otherwise.

I suppose I could write such a method myself, but I'm more interested in a built-in one.

In C# check that filename is *possibly* valid (not that it exists)

在System.IO名称空间中是否有一个方法可以检查文件名的有效性？例如，C:\foo\bar将验证，而:"~-*将不验证或者更棘手的是，X:\foo\bar会验证系统上是否有X:驱动器，但不会验证。我想我可以自己编写这样的方法，但我更感兴趣的是内置的方法。

问在C#检查中，文件名可能有效(不存在)
EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在C#检查中，文件名*可能*有效(不存在)EN

回答 13

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在C#检查中，文件名可能有效(不存在)
EN