Chris Maddock

@CharliePoole has written a nice blog on the issue regarding conflict between different versions of the NUnit Console and NUnit VS adapter: http://charliepoole.org/technical/nunit-engine-version-conflicts-in-visual-studio.html

@JVimes I like it - would you be willing to submit a pull request for this? In terms of implementation, this very similar issue describes how I'd personally go about...

Tagging low priority as this is an uncommon thing to hit, but we'd welcome the contribution none-the-less if you're willing, @JVimes

That's a very reasonable point! With the console/engine, I think it's a little easier to allow test running on older platforms. "Agent extensions" are something we want to tackle anyway,...

Now we're a little closer, let's try and put some platforms to these assemblies. Here's my thoughts, to get us started: **Console** Two targets: .NET 4.x (latest) and .NET 5....

Thanks for reading through, Charlie. I think one thing I hadn't considered is that, with .NET 4.x being an in place upgrade, if we require net462 to run the console,...

I have nothing to add, all this sounds great to me!

Good find @aolszowka, this clearly isn't practical. Verified by looking at the code in `AggregatingTestRunner` - we need an equivalent of `RunTestsInParallel` for Explore. The only additional complexity over RunTestsInParallel...

@aolszowka Just reaslied we've never offered a workaround - adding the `--inprocess` flag should do the job, and I don't think will have any impact on performance either.

@nunit/engine-team - I wanted to create a standard-ish format for proposed v4 changes, partly so we can make sure any changes in behaviour (breaking or otherwise) are well considered and...