What a embarrassing failure on Microsoft's end, in multiple ways. Using a third-party like this (not just as a white-label Azure service, apparently, but for first-party stuff like .NET even), not having a solid migration path or fallback plan, not having proper control over the azureedge.net domain to allow its use to be continued regardless of the backing Edge CDN, the short migration time-line being a complete surprise to them. Everything about this seems like the stuff of amateur companies, not one of the supposedly leading hyperscaler clouds.
this post was submitted on 28 Dec 2024
13 points (93.3% liked)
.NET
1512 readers
1 users here now
Getting started
Useful resources
IDEs and code editors
- Visual Studio (Windows/Mac)
- Rider (Windows/Mac/Linux)
- Visual Studio Code (Windows/Mac/Linux)
Tools
Rules
- Rule 1: Follow Lemmy rules
- Rule 2: Be excellent to each other, no hostility towards users for any reason
- Rule 3: No spam of tools/companies/advertisements
Related communities
Wikipedia pages
- .NET (open source & cross platform)
- .NET Framework (proprietary & Windows-only)
founded 2 years ago
MODERATORS
Less than 3 weeks while people are on vacation... I'm sure this will go smoothly