Better way to get the base directory?

Question

I have this code to load a config file and read all the values and it works fine when running the application but of course fails on team city because the appdomain\'s base

Answer 1

string baseDirectory=Application.StartupPath.Split(Path.DirectorySeparatorChar)[0];

Application startup path will return the path where exe is kept, we will split this using "\" and get the base directory as "C:" for example,

Answer 2

Your question is a bit unclear. I don't really know if this is what you want.

I typically use AppDomain.CurrentDomain.BaseDirectory

Alternatives

• Path.GetDirectoryName(Assembly.GetExecutingAssembly().Location)
• Environment.CurrentDirectory

Answer 3

string origAssemblyLocation = Assembly.GetExecutingAssembly().CodeBase;

Per MSDN:

Assembly.CodeBase Property

Gets the location of the assembly as specified originally

Answer 4

I like to make my classes configurable - for example they get the folder name as a parameter in their constructor. This makes it possible to test with different config files.

In test code we use:

TestContext.TestDeploymentDir

This is the testrun folder, where all assemblies for a test run are copied into, together with the test deployment items. We 'deploy' our unit test config files to the test run folder - this can be specified in the testrunconfig dialog in visual studio.

For our production code we pass

Assembly.GetExecutingAssembly().Location

to the constructor, which works for us.

Answer 5

try this one:

  Module[] modules = Assembly.GetExecutingAssembly().GetModules();
  return Path.GetDirectoryName(modules[0].FullyQualifiedName);

Answer 6

have you tried getting the FileName of the current process' MainModule?

System.Diagnostics.Process.GetCurrentProcess().MainModule.FileName

Or GetEntryAssembly()?

System.Reflection.Assembly.GetEntryAssembly().Location