On 2011-11-28, Andrew Arnott wrote:
> The documentation is poor, I agree. I had to stumble around quite a bit
> before I figured out how to use it properly myself. I believe the
> difference may be that CallContext.*Logical*SetData requires the value to
> be serializable, so that it can be clone
The documentation is poor, I agree. I had to stumble around quite a bit
before I figured out how to use it properly myself. I believe the
difference may be that CallContext.*Logical*SetData requires the value to
be serializable, so that it can be cloned and applied to other threads,
perhaps even
On 2011-11-27, Andrew Arnott wrote:
> I am successfully using CallContext.LogicalSetData myself for other logical
> thread tracking purposes in my application so I have reason to believe it
> works -- I just don't know why log4net isn't working. Any ideas?
LogicalThreadContext uses SetData rathe
What is the "hard problem" in your application, where your intuition tells you
Log4net is going to be helpful? How can we help you?
Richard J. Pennenga
Software Developer
Angel Medical Systems, Inc.
T: 732-542-5551 x110
F: 732-542-5560
rpenne...@angel-med.com
www.angel-med.com [cid:image001
Hi
Try adding this node:
On 28 November 2011 14:56, Rob Richardson wrote:
> Greetings!
>
> ** **
>
> I originally wrote an application to use rotating files that rotated by
> date, but log4net has a long-standing unfixed bug that prevents cleaning up
> old dated log files, and our cust
Greetings!
I originally wrote an application to use rotating files that rotated by date,
but log4net has a long-standing unfixed bug that prevents cleaning up old dated
log files, and our customer is not willing to accept log files that grow
without bound. Therefore, I tried to change the conf
