<div>
In the traditional n-layer architecture, logging is a cross-cutting concern (i.e. it has no particular home as it is shared functionality) and is therefore in an assembly of its own (maybe with other cross-cutting concerns such as policy settings) which is then referenced by your other layers.<br />
<br />
Your &quot;logging&quot; would have all the configuration settings it needs, the other layers would just call the functions in that layer and everything should play nicely.
</div>


<div>
Alternatively you would give you Web layer a means to initialise the BLL from the config, rather than the BLL needing direct access to it.<br />
<br />
What exception are you getting? If your BLL is a class library you will have to manually add a reference to the System.Configuration assembly.
</div>


<div>
I have used a very nice approach when accessing web specific settings within the other layers of your application. If you are using an IoC container then great, if not, you definitely need to start using one within your application.<br />
<br />
This example is detailed in the following article and simply maps a dictionary of key/value pairs to an interface. That interface instance will then be passed to your other layers through dependency injection.<br />
<br />
<a href="http://blog.mirajavora.com/elegant-app-settings-factory/" rel="ugc">http://blog.mirajavora.com/elegant-app-settings-factory/</a><br />
<br />
The great things about the appSettings is that it is exposed in .NET code as a dictionary, hence it works perfectly in this situation.
</div>


<div>
Thanks<br />
<br />
I've tried the system.configuration in the .cs file<br />
now i'm getting the following<br />
&quot;Unreachable Code Detected&quot; on the &quot;MyNS&quot; word<br />
<br />

<pre><code class="code-1 nolinks" id="code-20-40461473-1"><span> catch (Exception ex)</span>
<span>            {</span>
<span>                throw ex;</span>
<span>                MyNS.ErrorLog.clsError.RegisterErrorInLogFile(System.Configuration.ConfigurationManager.AppSettings[&quot;ErrorPath&quot;].ToString(), &quot;DAL_MyAccount.cs&quot;, &quot;UpdateScheduledReportData()&quot;, ex.Message);</span>
<span></span>
<span>            }</span>
</code></pre>
<br />
I've got the NS added to references &nbsp;folder<br />
MyNS.ErrorLog<br />
<br />
and i'm also <br />
using MyNS.ErrorLog;<br />
at the top of the file!?
</div>


<div>
<div class="content wysiwyg-content">
Hi<br />
<br />
I have 3 layers:<br />
WEB APP<br />
BLL<br />
DAL<br />
<br />
I have the error log system path stored in web.config<br />
<br />
I now want to use this app key in the BLL and DLL logic layers to write to log files when an error occurs<br />
i.e. on catching exeption:<br />
<br />

<pre><code class="code-1 nolinks" id="code-10-28565351-1"><span>myNS.ErrorLog.clsError.RegisterErrorInLogFile(System.Configuration.ConfigurationManager.AppSettings[&quot;ErrorPath&quot;].ToString(), &quot;DAL_MyAccount.cs&quot;, &quot;UpdateScheduledReportData()&quot;, ex.Message);</span>
</code></pre>
<br />
<br />
however, it error on<br />
System.Configuration.Confi<wbr />gurationMa<wbr />nager.AppS<wbr />ettings[&quot;E<wbr />rrorPath&quot;]<wbr /><br />
as its in a different project<br />
<br />
any ideas what code i need?
</div>
</div>


Hi

I have 3 layers:
WEB APP
BLL
DAL

I have the error log system path stored in web.config

I now want to use this app key in the BLL and DLL logic layers to write to log files when an error occurs
i.e. on catching exeption:

(CODE)


however, it error on
System.Configuration.ConfigurationManager.AppSettings["ErrorPath"]
as its in a different project

any ideas what code i need?

accessing web.config key from BL and DAL layer?

The successor to Active Server Pages, ASP.NET websites utilize the .NET framework to produce dynamic, data and content-driven web applications and services. ASP.NET code can be written using any .NET supported language. As of 2009, ASP.NET can also apply the Model-View-Controller (MVC) pattern to web applications

ASP.NET

C# is an object-oriented programming language created in conjunction with Microsoft’s .NET framework. Compilation is usually done into the Microsoft Intermediate Language (MSIL), which is then JIT-compiled to native code (and cached) during execution in the Common Language Runtime (CLR).