Hero6 icon indicating copy to clipboard operation
Hero6 copied to clipboard

Published 20 hours ago • verified publisher icon LateStartStudio

[General] .NET Standard and .NET Core

Open persn opened this issue 7 years ago • 7 comments

Now that Visual Studio 2017 is out and NET Standard is hot potato we should look at upgrading our code base to use NET Standard so that we hopefully can run Hero6 in .NET Core one day.

persn avatar Mar 09 '17 16:03 persn

We're going to have to put this on hold for now as Paket doesn't play nice with the new Visual Studio 2017 project templates. .NET Core and .NET Standard apparently uses a new standard for structuring .csproj, and Paket isn't able to make the distinction. I think this may be resolved in their pre-releases, but we'll wait for it to be included in their release fsprojects/Paket#2143.

persn avatar Mar 10 '17 23:03 persn

Paket v4.0 is maybe coming out in a few weeks, that would be good time to revisit this topic

persn avatar Mar 12 '17 17:03 persn

Paket v4.0 is out and I believe it is working as it should, but I think we're going to wait until .NET Standard v2.0 is out, it's supposed to be released sometime spring 2017

persn avatar Mar 23 '17 20:03 persn

It looks like .NET Standard 2.0 is in preview state now, it will most likely be included in VS 2017 15.3 which is also in preview state. https://twitter.com/terrajobst/status/862472762467655680

persn avatar May 11 '17 01:05 persn

Actually .NET Standard will be released in VS 2017 15.4 instead, go figure https://www.visualstudio.com/en-us/news/releasenotes/vs2017-preview-relnotes

persn avatar Aug 29 '17 18:08 persn

.NET Standard 2.0 is finally out with the release of VS2017 15.4 today, so I'll be looking into converting our code base to the new standard in the near future

persn avatar Oct 12 '17 20:10 persn

The Hero6.MonoGamePipeline project still hasn't been converted because .NET Core isn't supported for that project type

persn avatar Jan 12 '19 17:01 persn