Jamie Cansdale

My main concern with making, `UIThread = true` the default is that it could hide potential issues when code is executed on a background thread. There is now a requirement...

@sharwell, It was a bit of a rushed example. You're right it wouldn't work consistently in its current form. With `ReuseInstance = false` it would be terribly inefficient. Here is...

@dgriffen I wondered if it might be some kind of flag rather than an actual priority?

@CharliePoole, Here is the output from two tests using simply `dotnet test`. ``` C:\Source\Scratch\TestsXproj>dotnet test Project TestsXproj (.NETCoreApp,Version=v1.0) was previously compiled. Skipping compilation. NUnit .NET Core Runner 3.4.0 Copyright (C)...

@rprouse, Here's my project.json for reference: ``` json { "version": "1.0.0-*", "dependencies": { "NUnit": "3.4.1", "dotnet-test-nunit": "3.4.0-beta-2" }, "testRunner": "nunit", "frameworks": { "netcoreapp1.0": { "imports": "dnxcore50", "dependencies": { "Microsoft.NETCore.App": {...

Looks rather like it. :)

@mpoettgen I think you could use: `AppContext.BaseDirectory`. Just in case anyone is tempted to use this in a NuGet package. This doesn't currently mean what you probably think it means....

The simplest way would perhaps be to save them in the codebase of the target test assemblies (e.g. `bin\Debug\netcoreapp1.0` and `bin\Debug\net451\win7-x64`). Alternatively, we could append the TFM/RID like this: `TestResult-netcoreapp1.0.xml`...

I've been playing with a multi-framework project today and noticed that 'dotnet-test-nunit' doesn't currently work with classic .NET assemblies. I wonder if this could be related? Here is the repro:...

> #54 fixes this issue which was originally reported in #45. Do you know what this fix does exactly? It seems strange for .NET 4.5.1 to be taking an dependency...