Aah, that's true. I just removed the copied App.config files of my
library projects and logging still works! I.e., you only need to provide
the section in the AssemblyInfo.cs file for each project.

This solutions makes no sense to me, too. I'm quite new to .NET and
log4net and don't know what happens under the hood if a .NET
applications starts. I'm not sure whether this is a log4net or .NET
issue, maybe a log4net developer could help out with an explanation...

Best regards,

Ulli

> -----Original Message-----
> From: Muchhala, Raj [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, May 10, 2006 9:59 PM
> To: Log4NET User
> Subject: RE: Problems logging
> 
> 
> >> This occurs for me, if I add another project to my 
> solution that does
> not contain the log4net logger configuration
> 
> Interesting... that's exactly what I had done to both 
> projects.  I did get it to work but the solution makes no 
> sense to me:  I added a log4net declaration to the 
> global.aspx.vb page.  The working project had this line b/c I 
> was logging from these events.
> 
> Why in the world would that have resolved the issue???
> 
> Note:  I did NOT have to add a separate log4net config for 
> the referenced (and logging) assembly.
> 
> -----Original Message-----
> From: Hafner Ullrich [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, May 10, 2006 4:27 AM
> To: Log4NET User
> Subject: RE: Problems logging
> 
> 
> Hi Raj,
> 
> I also noticed that logging suddenly stops for my VS 
> solutions. This occurs for me, if I add another project to my 
> solution that does not contain the log4net logger 
> configuration. Logging works for me only if I have the 
> log4net config files in all projects. So try to add the 
> following log4net configuration in ALL of your projects: 
> 
> In the file AssemblyInfo.cs add:
> // Configure Log4Net using the XML properties
> [assembly: XmlConfigurator()]
> 
> Add a App.config file that contains the log4net configuration section.
> 
> Best regards,
> 
> Ulli 
>  -----Original Message-----
> From: Muchhala, Raj [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, May 09, 2006 8:51 PM
> To: [email protected]
> Subject: Problems logging
> 
> 
> I have two applications that use log4net (1.2.9.0)  and both 
> are configured the exact same way.  Yesterday, one of the 
> applications suddenly stopped logging.  A trace of the two 
> apps revealed the
> following:
> 
> App One (Does not work)
> 
> log4net: log4net assembly [log4net, Version=1.2.9.0, 
> Culture=neutral, PublicKeyToken=b32731d11ce58905]. Loaded 
> from [c:\windows\microsoft.net\framework\v1.1.4322\temporary 
> asp.net 
> files\gmportal\8786bfdf\bf1184a3\assembly\dl2\e56bfd36\a06700a
> 1_f972c601
> \log4net.dll]. (.NET Runtime [1.1.4322.2300] on Microsoft Windows NT
> 5.2.3790.0)
> log4net: DefaultRepositorySelector: defaultRepositoryType 
> [log4net.Repository.Hierarchy.Hierarchy]
> log4net: DefaultRepositorySelector: Creating repository for 
> assembly [Test.Flip, Version=1.0.0.0, Culture=neutral, 
> PublicKeyToken=null]
> log4net: DefaultRepositorySelector: Assembly [Test.Flip, 
> Version=1.0.0.0, Culture=neutral, PublicKeyToken=null] Loaded 
> From [c:\windows\microsoft.net\framework\v1.1.4322\temporary 
> asp.net 
> files\gmportal\8786bfdf\bf1184a3\assembly\dl2\eb66b878\20ef79a
> 0_f972c601
> \Test.Flip.dll]
> log4net: DefaultRepositorySelector: Assembly [Test.Flip, 
> Version=1.0.0.0, Culture=neutral, PublicKeyToken=null] does 
> not have a RepositoryAttribute specified.
> log4net: DefaultRepositorySelector: Assembly [Test.Flip, 
> Version=1.0.0.0, Culture=neutral, PublicKeyToken=null] using 
> repository [log4net-default-repository] and repository type 
> [log4net.Repository.Hierarchy.Hierarchy]
> 
> App Two (Works)
> 
> log4net: log4net assembly [log4net, Version=1.2.9.0, 
> Culture=neutral, PublicKeyToken=b32731d11ce58905]. Loaded 
> from [c:\windows\microsoft.net\framework\v1.1.4322\temporary 
> asp.net 
> files\myaccount\e53f1be8\731ae963\assembly\dl2\ba1d2fb7\901582
> 00_8373c60
> 1\log4net.dll]. (.NET Runtime [1.1.4322.2300] on Microsoft Windows NT
> 5.2.3790.0)
> log4net: DefaultRepositorySelector: defaultRepositoryType 
> [log4net.Repository.Hierarchy.Hierarchy]
> log4net: DefaultRepositorySelector: Creating repository for 
> assembly [Test.Flop, Version=0.0.0.0, Culture=neutral, 
> PublicKeyToken=null]
> log4net: DefaultRepositorySelector: Assembly [Test.Flop, 
> Version=0.0.0.0, Culture=neutral, PublicKeyToken=null] Loaded 
> From [c:\windows\microsoft.net\framework\v1.1.4322\temporary 
> asp.net 
> files\myaccount\e53f1be8\731ae963\assembly\dl2\d9d55618\c04c44
> 0e_8373c60
> 1\Test.Flop.dll]
> log4net: DefaultRepositorySelector: Assembly [Test.Flop, 
> Version=0.0.0.0, Culture=neutral, PublicKeyToken=null] does 
> not have a RepositoryAttribute specified.
> log4net: DefaultRepositorySelector: Assembly [Test.Flop, 
> Version=0.0.0.0, Culture=neutral, PublicKeyToken=null] using 
> repository [log4net-default-repository] and repository type 
> [log4net.Repository.Hierarchy.Hierarchy]
> log4net: DefaultRepositorySelector: Creating repository 
> [log4net-default-repository] using type 
> [log4net.Repository.Hierarchy.Hierarchy]
> log4net: XmlConfigurator: configuring repository 
> [log4net-default-repository] using file [E:/Log4Net.config] 
> watching for file updates
> log4net: XmlConfigurator: configuring repository 
> [log4net-default-repository] using file [E:/Log4Net.config]
> log4net: XmlConfigurator: configuring repository 
> [log4net-default-repository] using stream
> 
> -------------------------------------------------------------
> 
> So the first one never gets to the XmlConfigurator.   Anyone have any
> ideas why this would suddenly stop working?
> 
> Both apps use the assembly attribute method for defining the 
> config location 
> <Assembly: 
> log4net.Config.XmlConfigurator(ConfigFile:="Log4Net.config",
> Watch:=True)>
> Thanks,
> 
> Raj
> 
> 
> 
> This e-mail message and all attachments transmitted with it 
> may contain legally privileged and/or confidential 
> information intended solely for the use of the addressee(s). 
> If the reader of this message is not the intended recipient, 
> you are hereby notified that any reading, dissemination, 
> distribution, copying, forwarding or other use of this 
> message or its attachments is strictly prohibited. If you 
> have received this message in error, please notify the sender 
> immediately and delete this message and all copies and 
> backups thereof. Thank you.
> **************************************************************
> ************************
> This e-mail message and all attachments transmitted with it 
> may contain legally privileged and/or confidential 
> information intended solely for the use of the addressee(s). 
> If the reader of this message is not the intended recipient, 
> you are hereby notified that any reading, dissemination, 
> distribution, copying, forwarding or other use of this 
> message or its attachments is strictly prohibited. If you 
> have received this message in error, please notify the sender 
> immediately and delete this message and all copies and 
> backups thereof.
> 
> Thank you.
> **************************************************************
> ************************
> 

Reply via email to