Custom logging in a N-Tier Application
<p>I have an N-tier application, ASP.Net front end, then a .Net C# Business and Data Access Layer. I have created a simple custom logging library. This logging library is then used throughout my application i.e. Log.LogException and Log.LogMessage.</p>

<p>For this logging library I want to define the custom path for the logs folder created by my application. I initially thought the correct approach was to use an App.Config for my Logging library and then read in the path from there but the problem is that when I publish my Web App to its Target Location it copes all the binaries across including the logging DLL but not the accompanying App.Config.</p>

<p>This leads me to believe that this is not the right approach. I could do some "hack" to copy it across but that is a bad idea if it is not the best design approach.</p>

<p>Is this a supported design or am I going down the wrong route?</p>

<p>Thanks!   </p>
