CharliePoole

BTW this issue is a great example of potential work, which we would want to include in both the main (3.13) branch and the 4.0 development branch. Suggest using it...

That's too bad. Of course I've worked around the issue by now anyway. Back when I asked if you'd accept a PR for the feature, I had time on my...

I made a change to the docs way back and submitted it to the docs project. Perhaps someone with access can look.

@Shiney IMO, that's cool! We're told to "remove duplication." That means we have to create it first. :-)

I imagine that the level of disruption differs for various legacy asserts... * Classic Asserts like Assert.AreEqual or Assert.Null - even I still use some of these. :-) * CollectionAsserts...

@OsirisTerje Something to think about however... If you deprecate in the 4.0 release and remove in the 5.0 release, and if NUnit you continue with the existing pace of major...

@janis-veinbergs That link is the NUnit framework, not the NUnit console runner, which is here: https://www.nuget.org/packages/NUnit.ConsoleRunner

Hi @michael77777777777 If you read through the comments, you'll see that this issue was actually about non-terminating agent processes when running in the STA. Failing to terminate correctly is a...

Yes, a new issue with details is most likely best. Threads in the example I worked were not hung but were merely waiting for the process to terminate. Once the...

Most likely needs code in RuntimeFramework. It has a pot of built-in knowledge about what to call things and was probably never updated for .NET Core.