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.

Sign up for GitHub

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

Jump to bottom

Publish guidance for using .NET CDNs, install scripts, and other resources for installer/archive acquition #9673

Open

richlander opened this issue Dec 31, 2024 · 0 comments

Member

richlander commented Dec 31, 2024 •

edited

Loading

We need to publish a document that covers several acquisition topics as a result of #9671.

Boils down to two key questions:

What are the best and simplest ways to acquire .NET?
What are the best patterns to use for users that want a high availability solution?

Ideally there are docs and sample code for each approach.

There will naturally be detailed questions, particularly for folks wanting a high-availability solution:

Which domains to use?
What should users do if those domains are down (AKA fallback)?
Who should the following be used: Direct links, releases JSON, and short links?
How should Visual Studio CDN best be used? Only via releases JSON by hard-coding links, or some other way?
Is there a way to know the status of the various .NET download servers?

What else?

richlander mentioned this issue

dotnet CDN tracking issue #9674

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment