Comment 1 for bug 1096902

Let's clarify the bug first. If I understand you correctly, the problem is not that you can't get trace output, but that NUnit is not intercepting it. That is, if you use a TraceWriter, the trace output goes where you tell it, but your event listener addin never sees it. Is that right?

If so, it makes sense. NUnit-console has never done anything with trace output. Through at least 2.5.10, it would capture be captured anyway, which seemed to be a waste of effort. Somewhere in the 2.6 series of releases, we decided to set a flag that tells the runner not to capture any trace output.

If I understand your bug correctly, you want the output to be captured so that your addin can get it.