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

Question

I have a web project like:

namespace Web {     public partial class _Default : System.Web.UI.Page     {         protected void Page_Load(object sender, EventArgs e)         {             lbResult.Text = PathTest.GetBasePath();         }     } } 

The method PathTest.GetBasePath() is defined in another Project like:

namespace TestProject {     public class PathTest     {         public static string GetBasePath()          {             return AppDomain.CurrentDomain.BaseDirectory;         }     } } 

Why it's display ...\Web\ while the TestProject assembly is compiled into bin folder(in other words it should display ...\Web\bin in my thought).

Now I got a troublesome if I modified method into:

namespace TestProject {     public class FileReader     {         private const string m_filePath = @"\File.config";         public static string Read()          {             FileStream fs = null;             fs = new FileStream(AppDomain.CurrentDomain.BaseDirectory + m_filePath,FileMode.Open, FileAccess.Read);             StreamReader reader = new StreamReader(fs);             return reader.ReadToEnd();         }     } } 

The File.config is created in TestProject. Now AppDomain.CurrentDomain.BaseDirectory + m_filePath will returen ..\Web\File.config (actually the file was be copied into ..\Web\bin\File.config), an exception will be thrown.

You could say that I should modified m_filePath to @"\bin\File.config". However If I use this method in a Console app in your suggest, AppDomain.CurrentDomain.BaseDirectory + m_filePath will return ..\Console\bin\Debug\bin\File.config (actually the file was copyed into .\Console\bin\Debug\File.config), an exception will be thrown due to surplus bin.

In other words, in web app, AppDomain.CurrentDomain.BaseDirectory is a different path where file be copyed into (lack of /bin), but in console app it's the same one path.
Any one can help me?

Answer 1

Per MSDN, an App Domain "Represents an application domain, which is an isolated environment where applications execute." When you think about an ASP.Net application the root where the app resides is not the bin folder. It is totally possible, and in some cases reasonable, to have no files in your bin folder, and possibly no bin folder at all. Since AppDomain.CurrentDomain refers to the same object regardless of whether you call the code from code behind or from a dll in the bin folder you will end up with the root path to the web site.

When I've written code designed to run under both asp.net and windows apps usually I create a property that looks something like this:

public static string GetBasePath()           {            if(System.Web.HttpContext.Current == null) return AppDomain.CurrentDomain.BaseDirectory;      else return Path.Combine(AppDomain.CurrentDomain.BaseDirectory,"bin"); }  

Another (untested) option would be to use:

public static string GetBasePath()           {            return System.Reflection.Assembly.GetExecutingAssembly().Location; }