我应该使用 AppDomain。 CurrentDomain。 BaseDirectory 还是 System.Environment。 CurrentDirectory?

我有两个 exe 文件在同一个文件夹,我可以运行 exe2从一个按钮在 exe1。今天我在一个远程(终端服务)会话上观察一个客户,exe2运行‘ File not found’错误失败,但是当我们检查时,exe1在同一个目录中。那么我应该使用 目录还是 System.Environment. CurrentDirectory呢?

谢谢

107249 次浏览

As I understand it, you should use BaseDirectory. CurrentDirectory could change over the course of the program's execution.

If you want to find files in the same directory as your application, AppDomain.CurrentDomain.BaseDirectory is the correct choice.

Environment.CurrentDirectory is a value that can and will change throught the course of running your application. For instance, using default parameters, the OpenFileDialog in WinForms will change this value to the directory where the file was selected from.

I usually use something like:

            string AppPath = System.IO.Path.GetDirectoryName(System.Reflection.Assembly.GetExecutingAssembly().GetName().CodeBase);
AppPath = AppPath.Replace("file:\\", "");

AppDomain.CurrentDomain.BaseDirectory returns the directory from where the current application domain was loaded.
System.Environment.CurrentDirectory returns the current system directory.
In your case AppDomain.CurrentDomain.BaseDirectory is the best solution.

In Visual studio 2010 test projects, if you enable deployment option of Edit test settings, AppDomain.CurrentDomain.BaseDirectory points to the TestResults\Out folder(not bin\debug). Although, default setting point to bin\debug folder.

Here I found convincing answer.

Why AppDomain.CurrentDomain.BaseDirectory not contains "bin" in asp.net app?

You should use AppDomain.CurrentDomain.BaseDirectory.

For example in a windows services application:

System.Environment.CurrentDirectory will return C:\Windows\system32

While

AppDomain.CurrentDomain.BaseDirectory will return [Application.exe location]

Another important factor to note is that AppDomain.CurrentDomain.BaseDirectory is a readonly property while the Environment.CurrentDirectory can be something else if necessary:

// Change the directory to AppDomain.CurrentDomain.BaseDirectory
Environment.CurrentDirectory = AppDomain.CurrentDomain.BaseDirectory;

I have also been through this few days back, as I was using

Environment.CurrentDirectory

as it was giving me issue on the production server but was working fine with my local server,

So, I tried with

System.AppDomain.CurrentDomain.BaseDirectory;

And it worked for me in both the Environment.

So, As all of them has said We should always go with

System.AppDomain.CurrentDomain.BaseDirectory;

as it checks the Current Domain directory for the path.

have a look for more information

Could not find a part of path error on server