log4net argument to LogManager.GetLogger

log4net
Andy White picture Andy White · Mar 25, 2009 · Viewed 82.8k times · Source

Why do most log4net examples get the logger for a class by doing this:

private static ILog logger = 
    LogManager.GetLogger(
    System.Reflection.MethodBase.GetCurrentMethod().DeclaringType);

Rather than just passing typeof(MyClass):

private static ILog logger = LogManager.GetLogger(typeof(MyClass));

Is there any other reason for doing this, beside the fact that the first option does not require you to type a specific class name?

Answer

Steven Lyons picture Steven Lyons · Mar 25, 2009

I think you've got the reason. I do it that way so I don't have to worry about the class name and can just copy and paste boiler plate code in a new class.

For the official answer, see: How do I get the fully-qualified name of a class in a static block? at the log4net faq

Related questions

log4net hierarchy and logging levels

This site says Loggers may be assigned levels. Levels are instances of the log4net.Core.Level class. The following levels are defined in order of increasing priority: ALL DEBUG INFO WARN ERROR FATAL OFF DEBUG seems to have lowest …

Read More
Setting a log file name to include current date in Log4j

I would like to set the log file name for a log4j and log4net appender to have the current date. We are doing Daily rollovers but the current log file does not have a date. The log file …

Read More
Log4net does not write the log in the log file

I have created a simple scenario using Log4net, but it seems that my log appenders do not work because the messages are not added to the log file. I added the following to the web.config file: <configSections&…

Read More