Since the new alfa of Paket, we can install it as dotnet global tool.
I've made a little sample script where I first install Paket and later use the existing module.
Target.create "InstallPaket" (fun _ ->
if not (File.exists paketExe) then
DotNet.exec id "tool" "install --tool-path \".paket\" Paket --version 5.182.0-alpha001 --add-source https://api.nuget.org/v3/index.json"
|> ignore
else
printfn "paket already installed"
)
When running fake.ps1 Build (or fake.sh Build) it adds paket, downloads dependencies and builds the code. This seems like a nice setup for a CI build.
Could we benefit from something similar in the Fake.DotNet.DotNet or Fake.Dotnet.Paket module?
Since the new alfa of Paket, we can install it as dotnet global tool.
I've made a little sample script where I first install Paket and later use the existing module.
When running
fake.ps1 Build(orfake.sh Build) it adds paket, downloads dependencies and builds the code. This seems like a nice setup for a CI build.Could we benefit from something similar in the
Fake.DotNet.DotNetorFake.Dotnet.Paketmodule?