nunit-core team mailing list archive

[T J B <tjb930@xxxxxxxxxxxxxx>]

Public bug reported:

In version NUnit 2.5 and before, I used to be able to use simple lines
like the following:

System.Diagnostics.Trace.WriteLine(System.Reflection.MethodBase.GetCurrentMethod().Name);

and this could aid diagnostics by causing the function name (and/or
values of variables) to be logged in NUnit's "Text Output" tab. However,
in versions NUnit-2.6.0.12035 and NUnit-2.6.0.12051, this useful
functionality has stopped working.

** Affects: nunitv2
     Importance: Undecided
         Status: New


** Tags: output text

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/974119

Title:
  System.Diagnostics.Trace.WriteLine("Doesn't work any more")

Status in NUnit V2 Test Framework:
  New

Bug description:
  In version NUnit 2.5 and before, I used to be able to use simple lines
  like the following:

  System.Diagnostics.Trace.WriteLine(System.Reflection.MethodBase.GetCurrentMethod().Name);

  and this could aid diagnostics by causing the function name (and/or
  values of variables) to be logged in NUnit's "Text Output" tab.
  However, in versions NUnit-2.6.0.12035 and NUnit-2.6.0.12051, this
  useful functionality has stopped working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunitv2/+bug/974119/+subscriptions