It doesn’t work down to the method level, but most people add a static ILog per class based on the class name. You would then set up your configuration to only log you’re class A.

Here is a very untested example of code and config that logs all warnings and errors, but just debug info from class A;

namespace Blah

{

   public class A

   {

      private static readonly ILog log = LogManager.GetLogger( typeof( A ) );

      public void Foo()

      {

         log.Info( "Log Something" );

      }

   }

   public class B

   {

      private static readonly ILog log = LogManager.GetLogger( typeof( B ) );

      public void Bar()

      {

         log.Info( "Log Something Else" );

      }

   }

}

<?xml version="1.0" encoding="utf-8" ?>

<configuration>

   <configSections>

      <section name="log4net"

        type="log4net.Config.Log4NetConfigurationSectionHandler, log4net" />

   </configSections>

   <log4net>

      <appender name="FileAppender" type="log4net.Appender.FileAppender">

         <layout type="log4net.Layout.PatternLayout">

            <ConversionPattern value="%d [%t] %-5p %P %c %m%n" />

         </layout>

      </appender>

      <root>

         <level value="WARN" />

         <appender-ref ref="FileAppender" />

      </root>

      <logger name="Blah.A">

         <level value="DEBUG" />

      </logger>

   </log4net>

</configuration>

Hope this helps. If you want to go down to the method level, I would suggest adding the method name into your logging string and filtering on that. You could create a logger per method, but that is overkill in my opinion. Anyone else have a better suggestion for the method level?

Rob Prouse