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

Keep an eye on https://github.com/dotnet/core/issues/9671 #2848

Open
Numpsy opened this issue Dec 27, 2024 · 1 comment · May be fixed by #2849
Open

Keep an eye on https://github.com/dotnet/core/issues/9671 #2848

Numpsy opened this issue Dec 27, 2024 · 1 comment · May be fixed by #2849

Comments

@Numpsy
Copy link
Contributor

Numpsy commented Dec 27, 2024

Description

I'm not sure how much of an issue this is, but for the record -

Microsoft announced at dotnet/core#9671 that some .NET resources are moving to new domains due to a CDN they use falling over.

As it stands, Fake.Runtime uses Microsoft.Deployment.DotNet.Releases to download information about .NET product releases - ref

let! productCollection = ProductCollection.GetAsync()

Looking at Microsoft.Deployment.DotNet.Releases I see dotnet/deployment-tools#419 was made to change the default domain used to download the product release list.

So - I wonder whether Fake.Runtime will need to be changed to either use the new URL, or be updated to a new Microsoft.Deployment.DotNet.Releases if one should be released

@richlander richlander linked a pull request Dec 27, 2024 that will close this issue
@richlander
Copy link

PR: #2849

This line will fail some time in 2025. It will need to change to the new CDN.

let downloadPath = sprintf "https://dotnetcli.azureedge.net/dotnet/Sdk/%s/%s" sdkVersion archiveFileName

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 a pull request may close this issue.

2 participants