Chris Maddock

New method as in dotnet new? I thought there wasn't a VS gui for that yet?

Or is the suggestion that we create the files by hand instead?

Thanks Rob. Those were the threads I was thinking of - looks like there's been some important updates in the last month though. Guess there might be a bit more...

Reopening, as although the portable agent change caused the problem, the fix might be best made here. Previously the agent could only run one assembly at a time. This was...

@dougkpowers - if that's the case, then sounds like I'm barking up the wrong tree. 😄 I'm not familiar with dotnet tooling, just looking at the code in this repo....

Have verified this - it also happens on every run, and isn't limited to cases with multiple assemblies. Unfortunately it's possibly a little nontrivial - as the TestListeners in dotnet-test-nunit...

Ok, I've dug further. In an ideal world, the agent would take care of running multiple assemblies, however, this isn't possible with `dotnet-test-nunit` as each assembly requires it's own testlistener,...

The latest agent now returns a full `test-run` rather than a `test-suite` - this allows it to run multiple assemblies, and prevents that functionality needing to be implemented in multiple...

I guess in many ways this is a discussion as to the role of the agent. Is it going to be a simple, version-agnostic pipe to the framework, or is...

Sorry @CharliePoole - had to go back to work earlier! Will answer this with your other comment over on https://github.com/nunit/nunit.portable.agent/pull/16 - save us having the conversation over two different places!