ColoredConsole | Reenabling colors in Xcode 's console | Command Line Interface library

NLog Config Variables can operate in two modes:

• Static mode - ${logLifetime}
• Dynamic mode - ${var:logLifetime}

Static mode works for all types of properties independent of their type, but they will not react to runtime changes.

Dynamic mode only works for properties of the type NLog Layout. MaxArchiveDays is integer type and will not work. See also https://github.com/NLog/NLog/wiki/Var-Layout-Renderer

As a work around you can update the NLog Configuration from code, and assign the property directly on the FileTarget-objects:

I guess you can try this:

Rebus.RabbitMq 7.2.0 has the ability to customize .DefaultQueueOptions(...) like you do with .InputQueueOptions(...) above – this means that your code can be extended to

Think you need to help NLog when having NLog.config as Embedded Resource:

The logger name is created a follows:

• When using Logger.GetLogger(string name) the name is used without changes
• When using LogManager.GetCurrentClassLogger() the name of the class is searched on the stacktrace. In some cases this could be tricky, as inlining and async tricks makes it hard to find the correct name.

In this case the usage of LogManager.GetCurrentClassLogger() isn't really needed and I recommend to replace that one with Logger.GetLogger(string name)

Please also note that your design of the fluent API is a bit unconventional - at least for the added properties in your example.

• There is already a fluent interface, see NLog.Fluent namespace
• Some properties would be better to add to the a context class (e.g. GDC, MDLC, see context in NLog) or added as a custom layout renderer

Think you are missing SetMinimumLevel:

With Rebus and Azure Service Bus, topics are created when

a) a publisher first publishes to it, or b) a subscriber first subscribes to it

When I compare your two code snippets, the two lines with

When you

Yes, on usual, you will get a project like this: