Skip to content

Conversation

@KevinRansom
Copy link
Contributor

Whilst analyzing this: #6271

I noticed and got irritated by the multiple dotnet clis we download, also the current script downloads a dotnet/cli, every single build when building fcs.

Anyway updated the script, to peek in the artifacts directory and see if dotnet cli has already been downloaded, if so then I use it.

Kevin

@KevinRansom KevinRansom requested a review from brettfo February 22, 2019 08:04

let dotnetExePath = DotNetCli.InstallDotNetSDK "2.1.403"
let dotnetExePath =
// Build.cmd normally downloads a dotnet cli to: <repo-root>\artifacts\toolset\dotnet
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does build.sh do this as well?

Also when @brettfo finishes up the arcade work it won't be build.cmd/build.sh anymore

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cartermp build.sh in fcs calls build.fsx :-)
and build.sh in root builds a makefile.

@KevinRansom KevinRansom merged commit 6346800 into dotnet:master Feb 22, 2019
@KevinRansom KevinRansom deleted the multipleclis branch February 28, 2019 04:28
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

Successfully merging this pull request may close these issues.

2 participants