Rob Prouse

Thanks for the info. Visual Studio 2017 and the new `csproj` format for .NET Core changed the test adapter API, so the `dotnet-test-nunit` adapter is now deprecated, so we won't...

I agree, suppressing headers doesn't trim it down much. We should decide what should be hidden and probably make the same changes in the console. What do you think minimal...

Very odd, I am not seeing the labels or the Pass/Fail when I run unit tests and I am pretty sure we are not outputting the pass/fail. Maybe it is...

@jcansdale it looks like the Pass/Fail labels are coming from #56

@jskeet it is all changing for the new .NET Core tooling, but I would be willing to put out one more release to hold people over, so if someone submits...

If I am reading this right, you are using `TestContext.CurrentContext.WorkDirectory` in a ValueSource from a static method. I am pretty sure that `CurrentContext` will be null because the test is...

Test directory is not available because of the restrictions of the portable profile. We hope to readd stuff like this with a netstandard version of NUnit

I set this to blocked as it is an NUnit issue, not a runner issue.

@MihaMarkic TestDirectory is in the new .NET Standard 1.6 version of the NUnit Framework which will be released with v3.6

The new CSPROJ format officially deprecates support for the `dotnet-test-*` test adapters for running unit tests. Tests will be run in VS and on the command line using the old...