-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[General] .NET Standard and .NET Core #122
Comments
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. |
Paket v4.0 is maybe coming out in a few weeks, that would be good time to revisit this topic |
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 |
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 |
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 |
.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 |
The Hero6.MonoGamePipeline project still hasn't been converted because .NET Core isn't supported for that project type |
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.
The text was updated successfully, but these errors were encountered: