.NET Core releases a single file path issue

Little scum · Posted on 2021-3-28 13:56:32

Using .NET Core 3.1 to release a single-file console application, running on a Linux system, the main thing the program code does is very simple, that isRead the configuration file output in the program directory！ However, when you publish a single file to run on Linux, it says that the file is not found.

The new .NET Core features release a single-file executable
https://www.itsvse.com/thread-8273-1-1.html

Be wary of System.Environment.CurrentDirectory to get the current directory
https://www.itsvse.com/thread-9464-1-1.html

Test code:

Login is visible.

The output is as follows:

AppDomain.CurrentDomain.SetupInformation.ApplicationBase:/var/tmp/.net/root/ImageWatermark/e5snojro.qyv/
Environment.CurrentDirectory:/root/test
AppDomain.CurrentDomain.BaseDirectory:/var/tmp/.net/root/ImageWatermark/e5snojro.qyv/

When publishing a .NET Core application as a single file, running it on a CentOS system, the program is self-extracted and released/var/tmp/.net/root/directory, and then call the program released in the directory, which can also explain why the program cannot find the configuration file.

solution

Using System.Environment.CurrentDirectory to read the program path, System.Environment.CurrentDirectory is indeed getting the current directory, but if program A calls program B and program B uses System.Environment.CurrentDirectory to get the directory. Then the directory obtained in the B program is no longer the directory where the B application is located; It becomes the directory where A is located.

[Source] .NET Core releases a single file path issue

Related Posts

Sections viewed