How do you stop linqpad from displaying the output of statements written to Debug.Writeline?

Question

Linqpad seems to put a listener into the debug.listeners collection and then present the outputs of trace to the results window, along side any of the results from the query itself.

Is there a way of telling linqpad not to do this but to leave the existing debug.listeners collection alone?

I have an assembly I'm calling from linqpad which writes trace out to a separate application but it appears that linqpad clears down the listeners and puts its own in, ideally I would like the existing listeners left in tact so I get our normal trace out of the library.

Thanks for any suggestions Tollo

score 8 · Answer 1 · edited Jun 01 '12 at 04:51

8

I had the same problem.

I am referencing a third party library (Google.GData.YouTube) that is outputting a bunch of trace information that I don't want. Joe's solution didn't work for me but the question gave me a clue and I worked around the problem by adding the following to my query.

Debug.Listeners[0].Dispose();

edited Jun 01 '12 at 04:51

Perception

79,279
19
185
195

answered May 31 '12 at 23:21

Peter

81
1
1

4

Thanks; although that didn't work for me I used `Debug.Listeners.Clear();` and it worked. – wangzq Apr 28 '15 at 23:13
Note that full namespace is System.Diagnostics.Debug.Listeners.Clear(); – BraveNewMath Jan 24 '17 at 22:36

score 6 · Accepted Answer · answered Mar 10 '11 at 03:14

6

If you go to Edit | Preferences | Advanced, and select 'Always use fresh app domains', does it make any difference?

answered Mar 10 '11 at 03:14

Joe Albahari

30,118
7
80
91

That worked, it no longer seems to either disable our trace listeners or put the output into the results window :) I set Always Use Fresh Application Domains to true. Not sure what that does but it seems to work. Thanks. – Tollo Mar 10 '11 at 10:02

How do you stop linqpad from displaying the output of statements written to Debug.Writeline?

2 Answers2