There is an unsaved comment in progress. You will lose your changes if you continue. Are you sure you want to reopen the work item?
Invalid configuration throws exception
When the NLog configuration is invalid LogManager.GetCurrentClassLogger throws an exception, even when throwsException is false (which is the default). NLog doesn't log this error to its internal error log file.
So, for the case of an invalid configuration I have to create some fallback mechanism that still allows me to log this error. Specifically, this means that I have to encapsulate the creation of the logger in a try catch block and either use low level means
to create my own log file or create an NLog instance with default values in code.
Is this intended behavior?