-
Notifications
You must be signed in to change notification settings - Fork 588
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
Announcement: The dotnet-fake
package and CliToolReference (Paket clitool
) is deprecated
#2465
Comments
@matthid just to clarify, although I know that local tools are the way forward, are you saying that installing |
@isaacabraham No, only |
In the alternatives bit:
I read that as saying fake-cli as a global tool is not supported. |
Ah ok I wanted to express that the support for v2 version of the SDK has ended, so there is no reason to stay on v2. And in v3 you can use local tools, which are recommended. |
I edited it a bit. |
maybe just make it clear in the first line that you can use global tools as well although local is preferred e.g.
|
- new AppVeyor Image Visual Studio 2019 - update fake 5.19.1 (previous 5.18.3) - replace deprecated fake CliToolReference, see fsprojects/FAKE#2465 - use .NET core SDK 3.1.200
* paket 5.243.0 (from 5.194.3) - supports netcoreapp3.1 * .NET core SDK 3.1.200, Appveyor image and update fake - new AppVeyor Image Visual Studio 2019 - update fake 5.19.1 (previous 5.18.3) - replace deprecated fake CliToolReference, see fsprojects/FAKE#2465 - use .NET core SDK 3.1.200 * use paket as dotnet tool see also [Announcement: The `dotnet-fake` package and CliToolReference (Paket `clitool`) is deprecated](fsprojects/FAKE#2465 * remve dependencyfrom fake-cli in paket.paket.dependencies (fake is used as dotnet tool now)
There has not been any activity in this issue for the last 3 months so it will be closed in 14 days if there is no activity. |
Description
Given that this way of distributing .NET tools is phased out by Microsoft itself (see dotnet/announcements#107) that announcement shouldn't surprise anyone.
Additionally, we have been hit by the design flaws of this approach multiple times, see #2097 and #2447. Debugging and fixing these issues is incredibly time-consuming and frustrating.
Therefore we will no longer push updates to the
dotnet-fake
package. In the future we might additionally use this package name to publish the standalone tool (today:fake-cli
), but as usual here in FAKE, we give people enough time to adapt.For quite a while the documentation already stated:
Alternatives
We still have all the alternatives:
dotnet tool install fake-cli
) or global (dotnet tool install fake-cli -g
) toolsdotnet tool install -g fake-cli
) - Keep in mind that Microsoft support for .NET SDK v2 has already endedSee https://fake.build/fake-gettingstarted.html#Install-FAKE
Next steps
dotnet-fake
will be removed.This includes the samples from https://github.com/FakeBuild/fake-bootstrap
dotnet-fake
will no longer be updated (the broken 5.19.0 release has been unlisted). It was already marked obsolete when dotnet-fake clitoolreference 5.19 Does not run :( #2447 was reported.5.19.1
the fake template will no longer offer to create new projects with thedotnet-fake
package.The text was updated successfully, but these errors were encountered: