logging-log4net-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <ni...@apache.org>
Subject RE: 3rd party assembly logging configuration
Date Tue, 01 May 2007 12:05:16 GMT
The log4net internal debugging can be enabled by setting an <appSetting>
in the application's config file:

  <add key="log4net.Internal.Debug" value="true"/>

This must go into the applications .config file (or if it is a web app
then the Web.config file).

Setting the XmlConfigurator attribute on your assembly should cause it
to load its configuration separately from the main application.

There is an example application that is included in the log4net download
that shows this behaviour.


This is made up of 3 assemblies.

SharedModule - this is an ordinary DLL, it uses logging, but does not
configure it.
SimpleApp - this is an EXE, it configures and uses logging.
SimpleModule - this is a DLL, that setups its own repository and
configures it.

To see the RepositoryAttribute and XmlConfiguratorAttribute have a look
at this example source file:


Nicko Cadell
log4net development

-----Original Message-----
From: minherz [mailto:minherz@gmail.com] 
Sent: 01 May 2007 12:38
To: log4net-user@logging.apache.org
Subject: RE: 3rd party assembly logging configuration

The subject of using repository is little cloudy for me, even after
documentation. If i want to have same hierarchical repository for my
but starting from different root, then i have to use Repository
attribute at
the assembly level of my library. Is it correct?
Do i have to enable internal debugging of log4net in both configuration
files or only in the application's configuration?
After i make use of different repository does the XmlConfigurer
attribute in
the assembly level of my library enough to force log4net loading
configuration from the different file?

Thank you.
View this message in context:
Sent from the Log4net - Users mailing list archive at Nabble.com.

View raw message