CharliePoole

I'm pretty much convinced that this is not a bug. 1. AppDomains are somewhat minimally supported in .NET Core. In particular, they cannot be created. 2. As a result, all...

@OsirisTerje Is this a won't fix for version 3? NUnit.ConsoleRunner.NetCore, executed directly or as a dotnet tool, only runs tests in-process. Since it targets .NET 6.0, that's how it runs...

@OsirisTerje @manfred-brands @poklau I could finish the PR by merging it into the correct branch but I don't feel confident enough about what this is doing. If changing the manifest...

That's good enough for me. :-)

Merging this into version4 failed, probably because it has gotten a bit out of date. As this is simple, I'll just redo it in both main and version4.

@poklau Actually, the merge of your PR turns out to have failed for an unrelated reason: one of the dependencies in our myget feed no longer existed, having been automatically...

We're currently recommending that folks stop using version 3.16.x and use either 3.15.5 or 3.17.0. If the issue reappears in 3.17.0, we can reopen this issue.

This has been an issue in several releases and been "fixed" several times in the past. It doesn't seem to be in the current main and version3X branches any longer.

The `cSpell.json` file is only useful if you always want a particular spelling to be handled the same way. This is a bit different. It has to do that we...

I think that just having the release notes on GitHub is the best solution. See below for a "but" :-) I wanted to put this out there as an issue...