NLog.LogManager.Configuration reload causes RichTextBoxTarget to create a new form

[nlog]

NLog.LogManager.Configuration reload causes RichTextBoxTarget to create a new form

[welcome]

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

[snakefoot]

Thank you for the feedback. If you can figure out where it issue is in the RichTextBoxTarget-source-code:

• RichTextBoxTarget.cs

Then we can look at improving the source-code.

[snakefoot]

You are also wellcome to enable the NLog InternalLogger and then post the output, and highlight where the unexpected behavior occurs.

This might help guesing where in the source-code the issue is.

[dwanboweb]

The problem seems to be in RichTextBoxTarget.DetachFromControl, which will set TargetRichTextBox to null. When setting NLog.LogManager.Configuration to a new value, the setter will call config.close, which will invoke Target.Close() and then RichTextBoxTarget.DetachFromControl(). This will make TargetRichTextBox of RichTextBoxTarget null, and it will also affect the new value of Configuration when the new value is itself.
var config = NLog.LogManager.Configuration; // do some thing to config NLog.LogManager.Configuration = config; // in the setter of Configuration, TargetRichTextBox of RichTextBoxTarget will be null, and the new value is itself, so it will also affect the new value of Configuration

[snakefoot]

Notice that you are allowed to add new LoggingRules to the active LogManager.Configuration, without doing reassign NLog.LogManager.Configuration = NLog.LogManager.Configuration;

The trick is calling NLog.LogManager.ReconfigExistingLoggers() after having done the changes, to commit/activate them.

[snakefoot]

Closing issue as resolved, due to inactivity