How to avoid loading LoggingConfiguration from app.config about nlog HOT 12 CLOSED

NLog will only auto-scan for possible locations that can contain an NLog Configuration (Ex. app.config), when creating NLog Logger and no NLog Configuration has been loaded already.

Try manually loading/assigning the NLog Configuration before the first NLog Logger is created (Ex. before calling LogManager.GetCurrentClassLogger() or LogManager.GetLogger()).

Maybe at application-startup before anything has happened, then just assign empty configuration:

LogManager.Configuration = new LoggingConfiguration();

from nlog.

In fact the code posted previsouly is already called at the beginning.
I tried to add LogManager.Configuration = new LoggingConfiguration(); right after the assembly load but, I face the exact same Exception, just sooner.

from nlog.

from nlog.

Sure here the main thread where the init of NLog is done

And here the thread which throw the exception (only Ms code here)

from nlog.

Not sure what the NLog-project can do about other threads throwing exceptions, when accessing app.config.

Again NLog will not probe app.config if you assign NLog LogManager.Configuration upfront, before creating the first NLog Logger.

Avoid using the LogManager.Configuration-property-getter. This means not doing it like this:

NLog.LogManger.Configuration ??= new LoggingConfiguration();

And not doing it like this:

NLog.LogManger.Configuration = NLog.LogManger.Configuration ?? new LoggingConfiguration();

from nlog.

I add the creation of the configuration on the very first line of my assembly entrypoint

And it seems to crash here

I downloaded the source and I will try to debug that

from nlog.

Looking forward to hear if you have any findings. Sounds like a bug if LogFactory-constructor is throwing exceptions, before having loaded the NLog-configuration.

from nlog.

Seems to come from static object initialization which occur on Assembly.load() done on my C++ cli side.
It's very difficult to debug because seems to have kind of timing issue. When I put breakpoint into static constructor of LogFactory, the exception isn't throw.

As I try to load the assembly which use NLog from a custom AppDomain where I set a different app.config, maybe the config isn't properly initialized when NLog try to read into

from nlog.

Yes not a big fan of static constructors, as type-load-exceptions are really nasty. But sadly enough this is currently the way that NLog hookup to the AppDomain-event-handlers to ensure automatic flush on application-exit.

from nlog.

Closing due to inactivity. Hopefully with NLog v6, then auto-loading and static-constructors will be removed.

from nlog.

Yes, I keep using my old v4 version with my own workarround until you release the V6. Do you have any ideas about when you when to release it ?

from nlog.

NLog is a spare time project, and with the current speed, then I guess NLog v6 RTM will be in year. But maybe a NLog v6 Preview will arrive in 3-6 months.

from nlog.