Behaviour when logging null arguments

[jpmnteiro]

When logging in 2.1.0, if the argument supplied to the logger is null, the message still gets logged/printed and the argument's place is empty.

However, in 3.0.0, the same situation results in the message being discard/not logged.

Code used to test the behaviour:

            Logger logger = LogManager.GetCurrentClassLogger();
            SimpleConfigurator.ConfigureForConsoleLogging();

            string t = null;
            logger.Info("Hello World.");
            logger.Info("Testing null: {0}", t);

Results in 2.1.0:
2014-06-13 10:33:28.4856|INFO|Snippets.TestNlog|Hello World.
2014-06-13 10:33:28.5586|INFO|Snippets.TestNlog|Testing null:

Results in 3.0.0:
2014-06-13 10:35:08.2735|INFO|Snippets.TestNlog|Hello World.

Thanks for the bug report, well take a look at it

[cvanbergen]

Hi @Xharze , I found the responsible commit for this behavior. As soon as a null parameter is passed, a System.NullReferenceException is thrown and therefor the entire log line will be discarded.

Thanks I'll take a look at the pull request soon