Hi Mihail,
Thank you for posting in the MSDN forum.
Actually I‘m not very sure that whether it is the debugger issue since this forum is to discuss the VS Debugger tool.
But I did some research about this issue, maybe you could get useful information.
Like this document “Configuring Tracing”:
Tracing is not enabled by default. To activate tracing, you must create a trace listener and set a trace level other than "Off" for the selected trace source in configuration; otherwise, WCF does not generate any
traces. If you do not specify a listener, tracing is automatically disabled. If a listener is defined, but no level is specified, the level is set to "Off" by default, which means that no trace is emitted.
So it seems that we could control the level to enable/disable different trace message.
I also found two cases about the similar issue, if possible, you could refer them:
Turning trace on and off + specifying filepath at runtime
Turning tracing off via app.config
Hope it could help, if there's any concern, please feel free to let me know.
Sincerely,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.
