When it comes to use file names, say, in saving reports on the disk or sending them as an attachment, they must conform OS restrictions.
Although we cannot rely on GetInvalidFileNameChars function due to its limitation, it is easy to create your own procedure that clean off the illegal characters from the given file name.
In my example I use a regular expression and a set of characters that should be replaced with the underscore by default.
I used this article.
Although we cannot rely on GetInvalidFileNameChars function due to its limitation, it is easy to create your own procedure that clean off the illegal characters from the given file name.
In my example I use a regular expression and a set of characters that should be replaced with the underscore by default.
/// <summary> /// Checks for invalid characters in the filename and changes them with underscore. /// </summary> /// <param name="_fileName"> /// The file name value. /// </param> /// <param name="_char2use"> /// The character to use instead of illegal characters. Underscore by default. /// </param> /// <returns> /// valid file name /// </returns> static client str makeFileNameValid(str _fileName, str 1 _char2use = "_") { str pattern = "[/:*?'<>|]"; str fileName; fileName = System.Text.RegularExpressions.Regex::Replace(_fileName, pattern, _char2use); fileName = strReplace(fileName , '\\', _char2use); return fileName; }
I used this article.
No comments:
Post a Comment