CharliePoole

@rprouse He has a point there. I can't find anything to tell me not to use this project. Probably we should go through each of the archived projects and make...

@rprouse We might want to add some further options as to what should be suppressed, but IMO --noheader should cut out the header, as it has always been defined, and...

This is similar to issue nunit/nunit#1241, which we fixed, except that it deals with WorkDirectory rather than TestDirectory. WorkDirectory didn't seem to need fixing in this way, since it is...

While your statement is correct, I'm not 100% sure what we should do about it. We might want to add other options to those four that are supported or it...

Can you clarify point 2? Is there something that doesn't work when you run the tests normally without the `/framework` option? We don't build the framework for a higher level...

On documentation... we currently only say "Examples: mono, net-4.5, v4.0, 2.0, mono-4.0" which doesn't tell you exactly what is supported and what isn't. We should at a minimum provide a...

@fandrei Since that's not a feature we use in NUnit, we would not need to build to the 4.7 framework because of it. Your code, of course, can take advantage...

@nepdev It would help us to know whether the same problem shows up in the standard NUnit 3 adapter, if you target a desktop version of .NET like 4.5. If...

@nepdev Thanks for checking! @rprouse Looks like this is particular to dotnet-test-nunit then.

For the NUnit 3 adapter, see nunit/nunit3-vs-adapter#47