nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

I haven't seen your note on the NUnit list yet, so I'll answer here.

In the past, NUnit was using transforms to create console output, not
reports - although you could redirect the console output to a file and
call it a report if you liked. XSL transforms are a logical way to go
for reports, but are overkill for console output.

In 2.6, we simply use Console.WriteLine to produce the console output.
For reports, we suggest that folks post-process the xml result report.

In 3.0, there are command-line options to specify the transforms and
actually create reports - separate from the console output.

Charlie

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

Title:
  NUnit.Util.Transform.resources missing from nunit.util.dll

Status in NUnit V2 Test Framework:
  New

Bug description:
  I'm running into an issue that is preventing me from running tests
  with 2.6 beta4.  The message that I am seeing is:

  Test results could not be formatted.
  Could not find any resources appropriate for the specified culture or the neutral culture.  Make sure "NUnit.Util.Transform.resources" was correctly embedded or linked into assembly "nunit.util" at compile time, or that all the satellite assemblies required are loadable and fully signed.

  Looking at the nunit.util.build file, around line 87, it looks like
  the lines that include the resource file in question into the build
  have been commented out.  Unless I am mistaken, uncommenting this
  information should fix this issue.

  Thanks,
  Ryan

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