Migrate to VS2017 /MSBuild15 / .NET Standard / .NET Core

[supermihi]

This PR resolves #255. See #257 for initial discussion.

TODO:

• Verify Net35 project can be removed
• Verify Portable40 project can be removed
• Verify signed packages "just work" when upgrading to new package (key file was converted)
• Set up build and tests for UnitsNet.WindowsRuntimeComponent (not sure yet if dotnet CLI compatible)
• See if UnitsNet.sln can be removed or renamed to UnitsNet.WindowsRuntimeComponent.sln if that is the only project that is not compatible with dotnet CLI.
• Set up .xml output for tests to \Artifacts\Logs\<TestProjectName>.xml files, currently blocked by NUnit support in dotnet CLI. XUnit seems to have found a workaround, so either wait for NUnit to do the same or switch to XUnit.
• Update README on new build targets (net35, netstandard1.0, WindowsRuntimeComponent)

[angularsen]

Fixes #262 when merged.

[angularsen]

Slowly moving towards completion. I spent some time redoing all the build scripts, but it now properly builds, tests, packs and publishes nugets via Appveyor CI.

https://www.nuget.org/packages/UnitsNet/3.65.0-alpha1
https://www.nuget.org/packages/UnitsNet.Signed/3.65.0-alpha1

[supermihi]

Wow, now you put some effort into this! :) Would you mind pushing the current alpha version of the serialization package to nuget, because there's currently no version on nuget that works with dotnet core?

[angularsen]

I had some issues building, but just pushed some manual nugets out now. They are prerelease versions -alpha3.

I must say, this whole vs2017 journey has not been entirely pleasant. It took a lot more time plow through than I'd like to admit, but I do like a lot of the concepts that dotnet CLI brings.

[angularsen]

Currently running into this issue: microsoft/vstest#445 (comment)

Tests refuse to run when the output dir is changed using <BaseIntermediateOutputPath> in the test project, and it is needed due to having multiple test projects in the same folder to share the source code.
Sigh.

[supermihi]

Sorry that I sort of "tricked" you into this effort. ;-) I naively assumed that it would be sufficient to remove a few lines in the *.csproj files and be happy with it. But I think it's worth the effort, as you say the direction Microsoft is heading with the dotnet CLI and the .NET Standard is a good one, though at the moment tooling and documentation ase pure chaos.

If there's any specific task you need help with please let me know; unless it's fixing the code-gerenating/build/pack/sign scripts, since I don't know Powershell and don't want to learn it ATM. :)

[angularsen]

Hah, no worries :-) It would have to be done at some point anyway, and your effort really helped get over those initial roadblocks, so thanks for that!
Did the nugets work out as expected?

[supermihi]

Yes, I'm using the alpha version including JsonNet serialization in a dotnetcore app, works like a charm. Thanks!! :)

[angularsen]

Cool! :-)

…

On Thu, Jun 8, 2017 at 10:05 AM Michael Helmling ***@***.***> wrote: Yes, I'm using the alpha version including JsonNet serialization in a dotnetcore app, works like a charm. Thanks!! :) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#261 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAwFaAFTM7AXP5Ne-kzpyRzxL1HOpqRAks5sB6tjgaJpZM4NvBEi> .

[angularsen]

Merged! Phew.. a lot of hurdles on the windows runtime component stuff, as well as nunit and xunit with the new dotnet test and dotnet xunit commands. Did not like having multiple test projects in the same folder for one thing.

Thanks a lot for putting in the effort here. Hopefully this is now fairly future proof and not too many things change when dotnet CLI 2.0 goes RTM.

[supermihi]

Thank you as well for finishing this! I can only hope that Microsoft's approach with .NET standard will help to simplify multi-target libraries in the future ...