Configuration changes at runtime not supported about nlog.targets.syslog HOT 4 CLOSED

Here is my code in old version of syslog. Hope it helps.

var config = LogManager.Configuration;
var syslogTarget = config.FindTargetByName<Syslog>(CNSTR_SYSLOG);
syslogTarget.SyslogServer = "some.syslog.server";
LogManager.Configuration = config;
LogManager.Configuration.Reload();
LogManager.ReconfigExistingLoggers();

from nlog.targets.syslog.

I just created a console application and found out that both the ColoredConsoleTarget and FileTarget behave as expected without reloading the configuration or reconfiguring loggers:

var coloredConsoleTarget = loggingConfiguration.FindTargetByName<ColoredConsoleTarget>(ColoredConsoleTargetName);
coloredConsoleTarget.Layout = "${message}";

var fileTarget = loggingConfiguration.FindTargetByName<FileTarget>(FileTargetName);
fileTarget.FileName = ".\\new-log.txt";

This is because those targets use target properties directly instead of loading them from configuration settings.

I thought that the InitializeTarget was called to reconfigure a target, but if it is already inited no reconfig happens 😞

I could simply add a ReInitialize method but I would prefer not breaking the NLog base Target API.
Moreover I would like to avoid adding a Reinit call to each and every configuration setter.

Maybe a ForceReinit or ReconfigExistingLoggers(force: true) would be useful...
Does @304NotModified have any suggestion on the expected behavior a target with complex configuration should have and a feasible and elegant solution?

from nlog.targets.syslog.

Isn't easy to reset the cached values in the setter?

Eg in the set of Server property, clear the current connection. IPropertyChanged is maybe a nice pattern.

from nlog.targets.syslog.

I have just implemented INotifyPropertyChanged to reinit the target.
I will try to refine the solution as soon as possible

from nlog.targets.syslog.