.NET Core 中的跨平台文件名处理

Question

How to handle file name in System.IO classes in a cross-platform manner to make it work on Windows and Linux?

For example, I write this code that works perfectly on Windows, however it doesn't create a file on Ubuntu Linux:

var tempFilename = $@"..\Data\uploads\{filename}";
using (FileStream fs = System.IO.File.Create(tempFilename))
{
    file.CopyTo(fs);
    fs.Flush();                    
}

Answer 1

You can also use Path.DirectorySeparatorChar as below:

 Console.WriteLine("..{0}Data{0}uploads{0}{{filename}}", Path.DirectorySeparatorChar);

Reference: MSDN

Answer 2

Windows using Backslash. Linux using Slash. Path.Combine set the right symbol :
Path.Combine Method - MSDN

Answer 3

Lots of good answers. I would just like to add that one can avoid having to specify the directory separator character by using Path.Combine

Example with the file relatively located at ".\\..\\toto\\app.config":

Path.Combine("..", "toto", "app.config");

Unfortunately, Path.Combine does not resolve a relative path to an absolute Path in .Net Core. Path.GetFullPath is here for that:

Path.GetFullPath(Path.Combine("..", "toto", "app.config"))

Answer 4

You can simply use slashes. Relative paths will work identically, and absolute paths can only be relative to the root of the main drive (as absolute paths starting with "c:" are not portable)

Answer 5

The original post is over a year old but I still ran into this issue. It seems to me like the use of dots in relative paths is also an issue.

A path like

".\\input\\mydata.csv" 

worked well on windows but not on unix. When changing the dot-notation for current directory to:

Path.GetFullPath(Directory.GetCurrentDirectory())

I had more success.

Answer 6

Of course forward slashes work fine - except when they don't . It is an older problem, but certainly LoadLibrary actually bit me in this regard. Please see https://stackoverflow.com/a/34708551/1318024 which discusses this. Even though we do expect Windows to handle path separators gracefully (which we do not expect for *nix!) it is best to use the path separator appropriate for the platform.

Answer 7

There are also problem with file name cases in linux. For instance if you have file name like Index.js and used in your code like index.js vice versa, you are having a problem too

Answer 8

I do development on windows and linux so relative path settings in json config are not always correct for the platform. Path.Combine doesn't help if you have a path separator in the config path. Using a Replace does the trick tho. Eg:

var root = "c:\\bob";
var dir = "somepath/fred";
var path = Path.Combine(root, dir);  // = c:\bob\somepath/fred

path.Replace('/', Path.DirectorySeparatorChar); // = c:\fred\somepath\fred on windows

Answer 9

// For Windows
public static char slashSeparator = Path.AltDirectorySeparatorChar;
// For Linux
// public static char slashSeparator = Path.DirectorySeparatorChar;

var dirPath = $"{slashSeparator }dir1{slashSeparator }dir2{slashSeparator }";

Microsoft Documentation

Answer 10

you can use this simple function:

private string get_platform_compatible_path(string path)
{
   return path.Replace('\\', Path.DirectorySeparatorChar).Replace('/', Path.DirectorySeparatorChar);
}