RE: Calling method

2005-06-08 Thread Nicko Cadell
Sent: 08 June 2005 13:07 > To: Jaroslaw Kowalski; Log4NET User > Subject: RE: Calling method > > Thanks for that, that's been a great help. > > I do have an OT question, if that's OK. > > I was wondering how you guys measure your methods etc. > > How can I ge

Re: Calling method

2005-06-08 Thread Jaroslaw Kowalski
sw.Nanoseconds); -- The code uses QueryPerformanceCounter() API. Jarek - Original Message - From: "Paul Cowan" <[EMAIL PROTECTED]> To: "Jaroslaw Kowalski" <[EMAIL PROTECTED]>; "Log4NET User" Sent: Wednesday, June 08, 2005 2:06 PM Subject: R

RE: Calling method

2005-06-08 Thread Paul Cowan
lto:[EMAIL PROTECTED] Sent: 08 June 2005 13:09 To: Log4NET User Cc: Paul Cowan Subject: Re: Calling method Hi Paul, Try this code (taken from NLog's LogManager): - public static Logger GetCurrentClassLogger() { StackFrame frame = new StackFrame(1, fals

Re: Calling method

2005-06-08 Thread Jaroslaw Kowalski
-- From: "Paul Cowan" <[EMAIL PROTECTED]> To: "Log4NET User" Sent: Wednesday, June 08, 2005 12:04 PM Subject: RE: Calling method Hi, I would like to know what the best practice is for implementing this. Any code examples would be greatly appreciated. Thanks Paul

RE: Calling method

2005-06-08 Thread Paul Cowan
Hi, I would like to know what the best practice is for implementing this. Any code examples would be greatly appreciated. Thanks Paul -Original Message- From: Frode Breimo [mailto:[EMAIL PROTECTED] Sent: 08 June 2005 10:22 To: Log4NET User Subject: Re: Calling method Hi I've

Re: Calling method

2005-06-08 Thread Frode Breimo
Hi I've only started looking at log4net myself and I'm using a similar approach. I started out with exactly the same solution as you describe, and of course I got the same result. What I did was to add a GetLogger method to my Logger class, this takes a string parameter containing the name o

RE: Calling method

2005-06-03 Thread Nicko Cadell
r. Cheers, Nicko > -Original Message- > From: Paul Cowan [mailto:[EMAIL PROTECTED] > Sent: 03 June 2005 12:11 > To: Log4NET User > Subject: RE: Calling method > > Thanks Niko, > > So is this the standard practice that I should include the > logger in each

RE: Calling method

2005-06-03 Thread Paul Cowan
-Original Message- From: Nicko Cadell [mailto:[EMAIL PROTECTED] Sent: 02 June 2005 20:13 To: Log4NET User Subject: RE: Calling method Paul, You are explicitly asking for the logger called 'Jkd.Vor.Utilities.Logger' and using that one logger instance.

RE: Calling method

2005-06-02 Thread Nicko Cadell
[EMAIL PROTECTED] > Sent: 31 May 2005 10:38 > To: Log4NET User > Subject: Re: Calling method > > Paul Cowan wrote: > > > > > > Hi all, > > > > > > > > I have my log4net functionality wrapped up in a logging > component, I > &g

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

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