Okay, so I noticed the problem after pasting this snippet in here...
MISSING THE ASSEMBLY NAME from the fully qualified ref... :S
Things are looking good!
-Original Message-
From: Zimney, Christopher M.
Sent: Sunday, April 03, 2005 2:42 PM
To: Log4NET User
Subject: RE: Publisher policy
Yes, in fact, it reports that the reference it's trying to address is a
"partial" reference...
=== Pre-bind state information ===
LOG: DisplayName = Version=1.1.11.0, Culture=neutral,
PublicKeyToken=ff1099cf15ab5fb8
(Partial)
LOG: Appbase =
file:///C:/Personal/HostSolution/HostSolution/Sample.Web
Sam,
Thanks for the good repro case, nice to see someone using the tests!
I created an issue to track this:
http://issues.apache.org/jira/browse/LOG4NET-21
I have fixed this in CVS and will look at what we can do about updating
the release.
Many Thanks,
Nicko
> -Original Message-
> From:
Nicko Cadell wrote:
Kevin,
Setting the BufferSize to any value less than or equal to 1 should have
the same effect; to log synchronously.
It didn't seem to be that way. It was 0 when it was logging sometimes at
best. Once we set it to 1, it seemed to log responsively as would be
expected. That ma
Do you get any binding errors in the log4net internal debug?
http://logging.apache.org/log4net/release/faq.html#internalDebug
Nicko
> -Original Message-
> From: Zimney, Christopher M. [mailto:[EMAIL PROTECTED]
> Sent: 02 April 2005 01:55
> To: log4net-user@logging.apache.org
> Subject:
Kevin,
Setting the BufferSize to any value less than or equal to 1 should have
the same effect; to log synchronously.
Previously you said "but the database is flaky at best. Sometimes it
will work, sometimes it just won't log anything" later you seem to
indicate that *nothing* at all is logged to
