In my application, I've got the following logging strategy/appenders:
This works very well throughout the whole application, until the very first line I'm starting the OWIN web host using the IAppBuilder
interface. As soon as I invoke WebApp.Start
, I noticed the following behavior:
Upon further investigation, I figured out that OWIN silently attached an instance of System.Diagnostics.DefaultTraceListener
and System.Diagnostics.TextWriterTraceListener
to the default trace/debug ouput, which may be the root of the problem. However, declaring the DefaultTraceListener
in app.config explicitly didn't help.
Is there any way I can configure OWIN to be less... sneaky?
You can remove the listener in startup code, eg:
Trace.Listeners.Remove("HostingTraceListener");
(Name from source code)
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With