1

Closed

throwExceptions="false" is useless. Automatic reconfiguration dies if load configuration failed on an app start with a exception

description

If configuration (NLog.config etc.) is broken on start it kills the Automatic reconfiguration permanently.
It has no workaround.
 
I use hot configuration changing (editing) and this case is very awful for me and for my industrial App.
I can't allowd any exceptions! At all.
 
I want the Automatic reconfiguration worked at any case.
Or in the next:
<nlog
autoReload="true"
throwExceptions="false"
 
What The Heck?
 
Tested on NLog 2.0.
Closed Oct 7, 2012 at 5:36 PM by Xharze
Moved to https://github.com/NLog/NLog/issues/116

comments

IliyaTretyakov wrote Feb 29, 2012 at 2:00 PM

I find out workaround:
LogManager.Configuration = new XmlLoggingConfiguration(ConfigPath);
+
FileSystemWatcher
Bye-bye