Merge .NET Standard Engine back into the main solution

I am worried about the code for the .NET Standard engine diverging from the full framework engine, so I would like to merge the source and projects back into mutlitarget csproj projects using the new Visual Studio 2017 project format. At the same time, or possibly in subsequent PRs;

• Include the .NET Standard engine in the main engine’s NuGet package and deprecate the old .NET Standard engine package.
• Figure out how to do multi-targeting of engine addins?
• Add a .NET Standard 2.0 engine for use in Xamarin and a possible future dotnet nunit.

[ChrisMaddock]

My opinions:

WRT the primary engine… do you feel it needs to have a .NET Standard build? Are there platforms where developers want to run the “full” engine under (e.g.) .NET Core? If so, we probably need a .NET Standard 2.0 primary engine.

I agree we do. At work, we’re currently running NUnit tests with .NET Core on Linux. No mono, so we’re currently using the vs adapter, which lacks the functionality we have in the console.

what happens to the desktop build? Do we still need it, or can we limit the primary engine to running on Core 2.0 compatible platforms?

My understanding is that the latter would drop our support for any platforms pre-net-4.6.1. (Correct me if I’m wrong!) I don’t think that’s a good idea - so we instead should be looking at two separate builds of the engine, one for .NET Standard (2.0?), and one for .NET Framework 2.0. I would expect that they can share the vast majority of code.

[ChrisMaddock]

Completed in https://github.com/nunit/nunit-console/pull/400 😄