Kristian Kristensen’s Blog

using NServiceBus;

namespace Odin
{
    public class Lite : IProfile {}
}

This class works as a marker for the classes who actually implement the profile specific behavior. My demo profile is just a copy of the OOB Lite profile from NServiceBus, so it’s implementation looks like this:

 public class LiteProfileHandler : IHandleProfile<Lite>, IHandleProfile, IWantTheEndpointConfig
    {
        public void ProfileActivated()
        {
            Configure.Instance.Configurer.
            ConfigureComponent<InMemorySagaPersister>(ComponentCallModelEnum.Singleton);
            if (this.Config is AsA_Publisher)
            {
                Configure.Instance.Configurer.
                ConfigureComponent<InMemorySubscriptionStorage>(ComponentCallModelEnum.Singleton);
            }

        }

        public IConfigureThisEndpoint Config {get;set;}
    }

The interesting part in regards to logging is in the class that handles logging for my Lite profile:

    public class LiteLoggingHandler : IConfigureLoggingForProfile<Lite>
    {
        public void Configure(IConfigureThisEndpoint specifier)
        {
            NServiceBus.SetLoggingLibrary.Log4Net(() => log4net.Config.XmlConfigurator.ConfigureAndWatch(
                new FileInfo(@"C:\log4net.config")));

            //Switch to this line of code to use the log4net section in app.config
            //NServiceBus.SetLoggingLibrary.Log4Net(
            //   log4net.Config.XmlConfigurator.Configure
            //     );
        }
    }

This sets up log4net to read the configuration defined in the file “C:\log4net.config”. Obviously you’d want this to point to an app specific directory, a relative one or by embedding it in the app.config of the application. Doing the latter can be done by this call:

NServiceBus.SetLoggingLibrary.Log4Net(
log4net.Config.XmlConfigurator.Configure
);

The contents of log4net.config is seen below. It includes some default colors for the different log levels and sets the log level to show all Debug events and higher. You could use this configuration file as a starting point, and/or embed it in your log4net section in the app.config file.

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <log4net debug="false">
    <appender name="console" type="log4net.Appender.ConsoleAppender">
      <layout type="log4net.Layout.PatternLayout">
        <param name="ConversionPattern" value="%d [%t] %-5p %c [%x] &lt;%X{auth}&gt; - %m%n"/>
      </layout>
    </appender>
    <appender name="ColoredConsoleAppender" type="log4net.Appender.ColoredConsoleAppender">
      <mapping>
        <level value="FATAL" />
        <foreColor value="Red" />
        <backColor value="White" />
      </mapping>
      <mapping>
        <level value="ERROR" />
        <foreColor value="Red, HighIntensity" />
      </mapping>
      <mapping>
        <level value="WARN" />
        <foreColor value="Yellow" />
      </mapping>
      <mapping>
        <level value="INFO" />
        <foreColor value="Cyan" />
      </mapping>
      <mapping>
        <level value="DEBUG" />
        <foreColor value="Green" />
      </mapping>
      <layout type="log4net.Layout.PatternLayout">
        <conversionPattern value="%date [%thread] %-5level %logger [%property{NDC}] - %message%newline" />
      </layout>
    </appender>

    <root>
      <level value="DEBUG"/>
      <appender-ref ref="ColoredConsoleAppender"/>
    </root>
  </log4net>
</configuration>

To start the generic host with your new profile you parse the fully qualified type name to the NServiceBus.Host.Exe:

NServiceBus.Host.Exe Odin.Lite

And you should see an output console with color.