Migrate projects to .NET Core Tools 1.0

[atifaziz]

The .xproj and project.json files (based on preview versions) need to be migrated to .csproj now that .NET Core Tools 1.0 is released.

Contributors not using Visual Studio 2017 will have to rely on IDEs like Visual Studio Code or other editors supported by OmniSharp. This may already be the case anyhow for those not on Windows.

[atifaziz]

Initial attempt didn't go so well; see dotnet/cli#5973.

[atifaziz]

So according to dotnet/sdk#335 and @DustinCampbell's words there:

The high-order bit here is that cross-gen is broken for .NET Framework projects on all platforms but Windows.

This is a step backward. Unfortunately for us, building is breaking on Windows.

[DustinCampbell]

Note later in that issue that I noted that I was able to get OmniSharp's build (which targets net46 and netstandard1.6) working on OSX/Linux with a bit of trickery.

[atifaziz]

Thanks @DustinCampbell, I noticed and will give it a crack as soon as I have the Windows side of things working.

[atifaziz]

According to nunit/dotnet-test-nunit#108, dotnet-test-nunit won't work with .NET Core Tools 1.0 anymore. Meanwhile, NUnitLite could serve as a workaround.

[atifaziz]

Closed by e11a96e