CharliePoole
CharliePoole
@MaYoT27 Thanks, that was very clear! For now, I'm postponing this issue to a future release. I'll mark it for V4 as it's easier to publish experimental releases there, without...
@manfred-brands It has been using 8.0.2 ever since we introduced the .NET 8.0 agent in version 3.19. It's possible that this is the first 3.x version >= 3.19 that the...
Of course, if the warning were never issued in such cases, then no change would be necessary in use of stderr vs stdout. As I think about it, I feel...
@czdietrich There's nothing to prevent defining your own `class NUnit.Framewok.TestCategory : NUnit.Framework.Category`. You'll get an error due to ambiguity in any test class using System.ComponentModel, which you can then fix...
@czdietrich Sure, it was just a thought and not just aimed at you but at anyone reading this, since it has been moved to the analyzer repo.
Reviewing my [earlier comment](https://github.com/nunit/nunit-console/issues/7#issue-171263904), two years later... 1. We now have standard locations where properly named extensions will be found. We also have the ability to specify other locations on...
Another quite old one but important if it is still true. I doubt that it is, so I've marked it for re-confirmation after we do the beta1 release. Moving it...
This one is subtly different from the other issue that used CSScript, and fails somewhat differently. The good news is that I can replicate it in the console runner, which...
@Methuselah96 Although @OsirisTerje already moved this to the 6.1 milestone, I have continued to experiment with it. Although I haven't had any success with your repro as provided, I'm including...
Well, the NUnit framework transforms all console writes from within tests to events. The runner that handles those events gets to decide whether or not to display them as well...