So, start-up path, not "adr", right?
If you have some code in some assembly, this call can give you the executing assembly:
string assemblyLocation = System.Reflection.Assembly.GetExecutingAssembly().Location;
Naturally, you can get the location of any other assembly, for example, the entry assembly, using
System.Reflection.Assembly.GetEntryAssembly();
etc. Basically, this way you find a location of a main executable module of some assembly, which is a file. (An assembly itself does not have to be a single file, even though VS only support creation of single-module assemblies; the file is also a module, not an assembly.)
Now, you can extract the directory path:
string exePath = System.IO.Path.GetDirectoryName(assemblyLocation);
Please see:
http://msdn.microsoft.com/en-us/library/system.reflection.assembly.aspx[
^],
http://msdn.microsoft.com/en-us/library/system.io.path.aspx[
^].
I don't understand how can you "get access to an exe file", and how is this related to WCF, but it looks like this is your problem. :-)
—SA