Skip to content
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

Paket dotnet tool doesn't run on 3.0 previews #3634

Closed
baronfel opened this issue Aug 9, 2019 · 7 comments
Closed

Paket dotnet tool doesn't run on 3.0 previews #3634

baronfel opened this issue Aug 9, 2019 · 7 comments

Comments

@baronfel
Copy link
Contributor

baronfel commented Aug 9, 2019

Description

running paket restore on the 3.0 preview7 runtime fails with the following error:

It was not possible to find any compatible framework version
The specified framework 'Microsoft.NETCore.App', version '2.1.0' was not found.
  - The following frameworks were found:
      3.0.0-preview7-27912-14 at [/usr/share/dotnet/shared/Microsoft.NETCore.App]

You can resolve the problem by installing the specified framework and/or SDK.

The .NET Core frameworks can be found at:
  - https://aka.ms/dotnet-download

I think we need a build of the paket tool that multi-targets to 3.0, because the default roll-forward strategy only supports going up a minor version (ie from 2.1 to 2.2).

@baronfel
Copy link
Contributor Author

baronfel commented Aug 9, 2019

@baronfel
Copy link
Contributor Author

baronfel commented Aug 9, 2019

setting DOTNET_ROLL_FORWARD_ON_NO_CANDIDATE_FX=2 in my build container sidesteps the issue, but we should either have some documentation around this or publish a multi-targeted build soonish.

@baronfel
Copy link
Contributor Author

baronfel commented Aug 9, 2019

Instead of the user having to set an environment variable, we could package a runtimesettings configuration file that opts-in to roll-forward on major versions: https://natemcmaster.com/blog/2019/01/09/netcore-primitives-3/#runtimeconfigtemplatejson

@matthid
Copy link
Member

matthid commented Aug 9, 2019

Same thing in fake: fsprojects/FAKE#2325

@baronfel
Copy link
Contributor Author

baronfel commented Aug 9, 2019

I wondered why this felt like deja-vu. Would you like me to replicate my PR over there?

@matthid
Copy link
Member

matthid commented Aug 10, 2019

Would you like me to replicate my PR over there?

Sure, would love to merge it :).
Didn't realize there was a fix for this which doesn't need upgrading the sdk

@baronfel
Copy link
Contributor Author

Closing, was fixed in #3635

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants