Ron, thanks very much for the suggestion - the Fix property did the job after I worked out (from the log4net source) that my custom properties had to implement IFixingRequired<http://logging.apache.org/log4net/release/sdk/log4net.Core.IFixingRequired.html>. Once I did that I then found http://piers7.blogspot.com/2007/07/log4net-in-aspnet-redux-implement.htmlwhich describes exactly my issue.
Can I suggest some additions to the doco? I've created an issue in JIRA with a patch - https://issues.apache.org/jira/browse/LOG4NET-170 - would appreciate any feedback. Cheers 2008/8/12 Ron Grabowski <[EMAIL PROTECTED]> > Have you tried setting the Fix property to All or Partial? > > > http://logging.apache.org/log4net/release/sdk/log4net.Appender.BufferingAppenderSkeleton.Fix.html > > ----- Original Message ---- > From: Jerry Shea <[EMAIL PROTECTED]> > To: log4net-user@logging.apache.org > Sent: Monday, August 11, 2008 12:30:43 AM > Subject: Re: ASP.NET, AdoNetAppender and deferred property execution > > Hi Everyone, > > Apologies for sending multiple messages about this, but I guess my initial > question was buried at the bottom of email#1. > > Does anyone have a idea as to how I can force properties to be resolved at > log time rather than flush time? > > Thx, Jerry > > > 2008/8/7 Jerry Shea <[EMAIL PROTECTED]> > >> Yes I have confirmed that this is the case - when the AdoNetAppender's >> buffer flushes then and only then are the properties evaluated. >> >> >> >
