[Update Request]: Microsoft.Dotnet.* (update CDN urls)

[a-mnich]

What type of update are you requesting?

Something else not listed

Current Package Identifier

Microsoft.Dotnet.*

Package Version

multiple

Please describe the changes you would like to see

As announced in dotnet/core#9671 the hoster of the CDNs https://dotnetcli.azureedge.net/ and https://dotnetbuilds.azureedge.net/ will soon seize operations due to bankrupcy.
It is recommended that users switch to the new CDN domains as quickly as possible.
While a majority of the newest versions Microsoft.Dotnet.*packages has already been switched to the new CDN by @mthalman (e.g. in PR #200316) there are still a lot of packages with the old domains remaining.

• A GitHub Search for https://dotnetcli.azureedge.net/ gets results in 620 files within this repository.
• https://dotnetbuilds.azureedge.net/ isn't used within winget-pkgs

Action steps:
Open PRs to switch the installer domain from https://dotnetcli.azureedge.net/ to builds.dotnet.microsoft.com for all packages found in the GitHub search.

[flo7000]

hello,
i'd like to do that but i have a question:
i should do a PR for each package, right?

and starting at which point of the path do i count it as a whole package? at "SDK" in that example?
/manifests/m/Microsoft/DotNet/SDK/6/6.0.122/Microsoft.DotNet.SDK.6.installer.yaml

and use the whole link "https://builds.dotnet.microsoft.com" (and the rest of the installer path stays the same right?)

[Dragon1573]

I should do a PR for each package, right?

I think you may need to create pull requests for each versions of these packages.

"Sparse checkout" feature is enabled on my local clone. Sparse checkout the directory /manifests/m/Microsoft/DotNet with --no-cone mode and try following command. You'll have to create such that LARGE amount of pull requests ...

22:06:14 D:\...\winget-pkgs  [master ≡] 1ms pwsh> C:\Applications\Git\Git\usr\bin\find.exe ./manifests/m/Microsoft/DotNet -type f -name '*installer.yaml' | C:\Applications\Git\Git\usr\bin\wc.exe -l
585

---

Note

It's easy using IDEs or editors to perform a string replacement and submitting them via a single PR. But it's hard (wasting time accurately) creating 585 for each of them. 😞

[flo7000]

okay, i understand, thank you!

so i can be sure that all the paths exist at the new domain? not that i'd have to test that too :D

[Dragon1573]

So I can be sure that all the paths exist at the new domain? not that I'd have to test that too :D

Neither can't I. I've just tested one URL and it's valid. There might need a script for automatically checking these URLs.