-
Notifications
You must be signed in to change notification settings - Fork 585
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
Remainder: Set RollForward once we upgraded to .NET core 3.0 #2325
Comments
Until fake is published for 3.x, it's not going to run on it successfully. Global tools are runtime-dependent, not self-contained, and so running them requires a compatible runtime to be present on the system. The runtime resolution rules can be found here, but the long and short of it is
It looks like you're hitting the third case, because FAKE is compiled for 2.1, which means it works on 2.1 and 2.2 runtimes. |
Well they introduced some roll-forward settings we "could" use: https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0#major-version-roll-forward -> We could add https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-2-1#roll-forward -> You can use |
Thanks for the answers! |
@rusanov-vladimir Thanks for confirming that this actually works ;) |
Ok, I'm labeling this as "extern" because dotnet SDK 3 is not yet released. I'm no longer playing around with previews. However, I would probably accept a PR updating all the required places. Considering there is a workaround I'll leave this open as a reminder until SDK v3 has shipped. Please feel free to remind me about this issue when that happened :) |
This should be solved in 5.16 due to #2372 |
I'm trying to run fake 5 script on ubuntu using latest .NET core 3 preview5.
I uninstalled previous SDK versions so it's the only .NET core version I got.
After installing global tool with
dotnet tool install fake-cli -g
I'm getting error above:
Seems to be similar to #1974.
Is there any reason why fake cannot run on dotnet core 3.0 preview?
The text was updated successfully, but these errors were encountered: