CharliePoole

Ouch! I'll take another look at this for 3.16.1.

@cw397 I created issue #1274 to deal with this problem in 3.16.1

@rprouse When you say "keep the async method" do you man keep it as it is... i.e. not true async and therefore not awaitable? On the general principal of not...

Bear in mind, we're talking about a major release, with lots breaking changes already in place. It's our third major upgrade in 22 years, so nobody can say we break...

BTW, one reason this problem exists in the first place is that the console runner never uses `RunAsync`. When I started working on the TestCentric GUI, I found I needed...

@nunit/engine-team @OsirisTerje I'm wondering what the true priority of the issue ought to be for this project. I made it "high" because my GUI needs it to be fixed if...

@jnm2 The current setup is that the thread used by the runner to invoke the engine is blocked in the agent, waiting for any commands to be executed. A thread...

That's quite true from an implementation point of view. I think the discussion here relates to whether the call to the public API blocks or not. Currently, we have both...

I built two simple runners using the same code. One targets net45 and the other net5.0. Visual Studio creates a non-sdk-style project using packages.config for net45 and an sdk-style project...

It occurs to me that this would not be a problem if all our agents were pluggable extensions. Then the extension service would just find them! I'm experimenting with this...