this post was submitted on 29 Dec 2024
6 points (100.0% liked)

.NET

1512 readers
1 users here now

Getting started

Useful resources

IDEs and code editors

Tools

Rules

Related communities

Wikipedia pages

founded 2 years ago
MODERATORS
erlingur
starman
Spyros
6
Critical: .NET Install links are changing - .NET Blog (devblogs.microsoft.com)
submitted 3 weeks ago* (last edited 3 weeks ago) by Kissaki to c/dotnet
1 comments fedilink hide all child comments
 

azureedge.net dotnet CDN URLs will cease to work sometime next year after January 15th.

One of two Azure CDN providers was Edgio, which filed for bankruptcy. CDN migration is in progress.

We expect that most users will not be directly affected, however, it is critical that you validate if you are affected and to watch for downtime or other kinds of breakage.

We maintain multiple Content Delivery Network (CDN) instances for delivering .NET builds. Some end in azureedge.net. These domains are hosted by edg.io, which will soon cease operations due to bankruptcy. We are required to migrate to a new CDN and will be using new domains going forward.

Affected domains:

  • dotnetcli.azureedge.net
  • dotnetbuilds.azureedge.net

Unaffected domains:

  • dotnet.microsoft.com
  • download.visualstudio.microsoft.com
  • Update dotnetcli.azureedge.net to builds.dotnet.microsoft.com
  • Update dotnetcli.blob.core.windows.net to builds.dotnet.microsoft.com

We also noticed that there is a lot of use of our storage account: dotnetcli.blob.core.windows.net. Please also search for it. The storage account is unaffected, however, it would be much better for everyone if you used our new CDN. It will deliver better performance.

you are viewing a single comment's thread
view the rest of the comments
[–] Kissaki 8 points 3 weeks ago

Really shows how even if you're using a big cloud provider, you're not safe from sudden systematic issues like a backing service becoming unavailable. I wasn't aware they directly integrated third-party providers like that.

There's an Azure migration path from Azure CDN to Azure Front Door.

I'm not too familiar with the Azure products. Surely Azure CDN was documented as backed by another company, and mindful use would have been aware of this provider dependency?

Still, I feel like the uniform Azure branding nudges users to trust it as one big, stable, long-term platform that can serve all your needs.