Add support for net standard

[clydevassallo]

I am currently calling running NUnit tests in a .NET Standard 2.0 project using the nunit.engine.netstandard NuGet package.

After running the tests, I would like to generate the NUnit2 xml report to pass it on to Specflow's report generator. Presently, NUnit.Extension.NUnitV2ResultWriter target .NET Framework so I cannot initialize the NUnit2XmlResultWriter and call the WriteResultFile() in my .NET Standard project.

[jnm2]

@ChrisMaddock Can addins target .NET Standard yet?

[CharliePoole]

@jnm2 Not to be overly picky, but they are called "Engine Extensions". The term "Addins" is used in NUnit in two ways: (1) a now-obsolete method of extending the v2 framework and (2) a proposed enhancement to engine extensions, which bundles extensions targeting multiple points and possibly multiple applications (e.g. engine and gui) into the same assembly. In anticipation of implementing the second, I used .addins as a file extension.

The desire for users to have the same extensions available in the .NET Standard "engines" is very natural and is one of the main reasons I thought that calling them "engines" was a bad idea.

[ChrisMaddock]

@JMM2, not yet unfortunately. There’s an updated .NET standard engine on a branch at the moment. Extensions are a little further down the list. 😊

[jnm2]

Oh, right. That makes sense.

Can we link this issue so we don't lose track of it?

[ChrisMaddock]

At the moment, the only source of this discussion is here: https://github.com/orgs/nunit/teams/engine-team/discussions/4

Turning that discussion into publicly visible issues is still on my todo list. 😞

[CharliePoole]

Moving this out of the 3.7 milestone while we discuss whether to support V2 output in dotnet core.