61

I need to get all dlls in my application root directory. What is the best way to do that?

string root = Application.StartupPath;

Or,

string root = new FileInfo(Assembly.GetExecutingAssembly().Location).FullName;

And after that,

Directory.GetFiles(root, "*.dll");

Which way is better? Are there better ways?

Sam
  • 7,252
  • 16
  • 46
  • 65
abatishchev
  • 98,240
  • 88
  • 296
  • 433

5 Answers5

87

AppDomain.CurrentDomain.BaseDirectory is my go to way of doing so.

However:

Application.StartupPath gets the directory of your executable

AppDomain.BaseDirectory gets the directory used to resolve assemblies

Since they can be different, perhaps you want to use Application.StartupPath, unless you care about assembly resolution.

abatishchev
  • 98,240
  • 88
  • 296
  • 433
Greg Dean
  • 29,221
  • 14
  • 67
  • 78
  • 10
    Application.StartupPath will be effected by "Working Directory" if it's set in the exe shortcut, or the process is started from another apps. I didn't realized it until much later, which had cost me days of sleepless night to troubleshoot what went wrong. – faulty Dec 12 '08 at 15:52
26

It depends. If you want the directory of the EXE that started the application, then either of your two examples will work. Remember though, that .NET is very flexible, and it could be that another application has linked to your EXE and is calling it, possibly from another directory.

That doesn't happen very often and you would probably have written if it did, but it is a possibility. Because of that, I prefer to specify which assembly I am interested in and get the directory from that. Then I know that I am getting all of the DLLs in the same directory as that specific assembly. For example, if you have an application MyApp.exe with a class in it MyApp.MyClass, then you would do this;

string root = string.Empty;
Assembly ass = Assembly.GetAssembly( typeof( MyApp.MyClass ) );
if ( ass != null )
{
   root = ass.Location;
}
Rob Prouse
  • 22,161
  • 4
  • 69
  • 89
8

This is an old question but I always used to use:

Environment.CurrentDirectory = Path.GetDirectoryName(Process.GetCurrentProcess().MainModule.FileName);

However, looking at the solutions in here I think some simple tests need to be done:

var r = new List<long>();
var s = Stopwatch.StartNew();

s.Restart();
string root1 = Application.StartupPath;
r.Add(s.ElapsedTicks);

s.Restart();
string root2 = Path.GetDirectoryName(Process.GetCurrentProcess().MainModule.FileName);
r.Add(s.ElapsedTicks);

s.Restart();
string root3 = Path.GetDirectoryName(new FileInfo(Assembly.GetExecutingAssembly().Location).FullName);
r.Add(s.ElapsedTicks);

s.Restart();
string root4 = AppDomain.CurrentDomain.BaseDirectory;
r.Add(s.ElapsedTicks);

s.Restart();
string root5 = Path.GetDirectoryName(Assembly.GetAssembly( typeof( Form1 ) ).Location);
r.Add(s.ElapsedTicks);

The results in ticks:

  • 49
  • 306
  • 166
  • 26
  • 201

So it seems AppDomain.CurrentDomain.BaseDirectory is the way to go.

eried
  • 398
  • 5
  • 15
1

If you want to get the application root folder path use below code sample.

string path =new DirectoryInfo(Environment.CurrentDirectory).Parent.Parent.FullName
Telan Niranga
  • 437
  • 3
  • 10
0

I use

Path.GetDirectoryName(new Uri(Assembly.GetEntryAssembly().CodeBase).LocalPath)

The Assembly.Location will point to the shadow copy if you use shadow copying, so using CodeBase is a better option, but CodeBase is a Url.

Someguy
  • 1
  • 1