Should targets added manually after configuration loaded already be initialized ?

[CamusGao]

Hi!
I have a config file in my case and i want to add a target manually after this config file loaded but this target is invalid and never initialized.
Should targets added manually after configuration loaded already be initialized ?

[welcome]

Hi! Thanks for opening your first issue here! Please make sure to follow the issue template - so we could help you better!

[snakefoot]

After having added the new target and configured the Logging-Rules, then execute this method:

LogManager.ReconfigureExistingLoggers()

It will update all Logger-objects to apply the updated Logging-Rules, and also initialize newly added Targets.

[CamusGao]

After having added the new target and configured the Logging-Rules, then execute this method:

LogManager.ReconfigureExistingLoggers()

It will update all Logger-objects to apply the updated Logging-Rules, and also initialize newly added Targets.

But I have no logger at all, this method name is a little confusing.

[snakefoot]

@gggxp If you don't have any Logger-objects or ILogger-objects, then I guess you don't need any targets (or any NLog configuration for that matter).

Again trust me. After having updated Logging-Rules and added NLog-Targets, then call this method:

NLog.LogManager.ReconfigureExistingLoggers();

[snakefoot]

Alternative you can make use of the fluent-API (Calling ReconfigureExistingLoggers is not necessary):

NLog.LogManager.Setup().LoadConfigurationFromFile().LoadConfiguration(builder => {
   // Dynamically adds the console-target after having loaded from NLog.config
   var consoleTarget = new ColoredConsoleTarget("console");
   builder.Configuration.AddRule(LogLevel.Info, LogLevel.Fatal, consoleTarget);
}));

[CamusGao]

@gggxp If you don't have any Logger-objects or ILogger-objects, then I guess you don't need any targets (or any NLog configuration for that matter).

Again trust me. After having updated Logging-Rules and added NLog-Targets, then call this method:

NLog.LogManager.ReconfigureExistingLoggers();

I do believe you and it works. but what i mean is the method named NLog.LogManager.ReconfigureExistingLoggers() looks like reconfiguring existing loggers although I have no logger at that time.The name dose not match its behavior.
Thank you so much and sorry for my poor english language and expression.

[snakefoot]

Yes method ReconfigureExistingLoggers does a lot of things, but its main-objective is to do a fast-refresh of the LoggingConfiguration, and update all existing Logger-objects by applying any updates to the Logging-Rules.

You are welcome to use the fluent-API and then you don't have to look at the confusing method name.

[snakefoot]

Closing as resolved