The log4net internal debugging can be enabled by setting an <appSetting> in the application's config file:
<appSettings> <add key="log4net.Internal.Debug" value="true"/> </appSettings> 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. examples\net\1.0\Repository 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: examples\net\1.0\Repository\SimpleModule\cs\src\Math.cs Cheers, Nicko ------------ Nicko Cadell log4net development http://logging.apache.org/log4net -----Original Message----- From: minherz [mailto:[EMAIL PROTECTED] Sent: 01 May 2007 12:38 To: [email protected] Subject: RE: 3rd party assembly logging configuration The subject of using repository is little cloudy for me, even after reading documentation. If i want to have same hierarchical repository for my library 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: http://www.nabble.com/3rd-party-assembly-logging-configuration-tf3668813 .html#a10267809 Sent from the Log4net - Users mailing list archive at Nabble.com.
