RE: Using machine.config for log4net configuration

2005-05-31 Thread Howard Weisberg
The way we do it is, we deploy our web application, along with two Windows services, a stand-alone executable, and all the library dlls they use (mostly shared), all in the same folder. We already had it set up this way before implementing logging. A single "Log.config" file in the shared folder is

RE: Using machine.config for log4net configuration

2005-05-31 Thread Conant, Patrick D
Having not received a response, I delved into the code a bit. It looks like Log4Net doesn't look in the machine.config file, so any settings there would never be read or used... Back to the drawing board... --p. -Original Message- From: Conant, Patrick D Sent: Friday, May 27, 2005 10:4

RE: A couple of questions and comments

2005-05-31 Thread Ron Grabowski
Yes, you can provide your own ILog, LogImpl, etc. I've been doing this for a while and posted a question: http://www.mail-archive.com/log4net-user%40logging.apache.org/msg01677.html asking if this was still the recommended way to do things in the latest version. The other link in that thread has

RE: A couple of questions and comments

2005-05-31 Thread Ron Grabowski
I agree that my quote about the 50-60 nanoseconds may have been misleading. Sorry if that confused anyone. As far as speed goes, I think things are fine just the way they are :) I use %c and %L in my conversionPatterns all the time and haven't noticed any kind of slow down. --- Schweizer Andreas <

Re: A couple of questions and comments

2005-05-31 Thread Jaroslaw Kowalski
If speed is an issue in your project you may need to look into certain optimizations that will be more applicatable for your project. Jaroslaw Kowalski, the author of NLog, states that log4net takes between 50-60 nanoseconds His implementation takes 5-10 microseconds to log to a file, and he say

RE: A couple of questions and comments

2005-05-31 Thread Schweizer Andreas
Hi list, hi Ron! first, thank you Ron for your detailed answer. > It sounds like designing and implementing your own interface > (using ILog as a guide) might suit your needs better. Here is > an example of an That's exactly true. If I understand it correctly, we can then simply provide our o

RE: Calling method

2005-05-31 Thread Paul Cowan
But I'm sure there is a way of doing this without defining a logger in each class. Somehow be able to drill down into the call stack. -Original Message- From: Graham Innocent [mailto:[EMAIL PROTECTED] Sent: 31 May 2005 10:38 To: Log4NET User Subject: Re: Calling method Paul Cowan wrot

Re: Calling method

2005-05-31 Thread Graham Innocent
Paul Cowan wrote: Hi all, I have my log4net functionality wrapped up in a logging component, I have my logger declare like so: namespace Jkd.Vor.Utilities { public class Logger { private static log4net.ILog log = log4net.LogManager.GetLogger(System.Reflection.MethodB

Calling method

2005-05-31 Thread Paul Cowan
Hi all,   I have my log4net functionality wrapped up in a logging component, I have my logger declare like so:   namespace Jkd.Vor.Utilities {   public class Logger   { private static log4net.ILog log = log4net.LogManager.GetLogger(System.Reflection.MethodBase.GetCurrentMeth