.NET Runtime update timeout

[trolleyboy]

Describe the bug

When opening file types that invoke extensions which use the .NET Runtime, this .NET Runtime Install Tool kicks off an update process. When on our corporate network, the updates time out as they seem to be blocked by our corporate firewalls. I can't quite work out if it's the initial PowerShell script that is blocked, or the subsequent dynamic URL for the actual .NET Runtime installer that is blocked.

Could we please get a list of URLs published that we can add to corporate firewall allow lists to ensure updates can be downloaded? A list similar to this: https://code.visualstudio.com/docs/setup/network

eg: some of the URL's I think I've identified by reviewing the dotnet-install.ps1 script...

• https://aka.ms/dotnet/STS/*
• https://dot.net/v1/dotnet-install.ps1

Additionally, if the update does timeout, it still seems to keep trying and never returns an error to the initial file type extension, so that extension sits waiting for a response and never starts. eg: the ARM Template Language Server.

Other Info:

Reproduction Steps
example: Open an ARM Template .json or Bicep .bicep file.

Expected behavior
.Net Runtime updates successfully, or returns a suitable error so that the original extension can continue to run.

Exceptions & Errors (if any)

Downloading .NET version(s) 7.0.12~x64 ....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... Error!
TIMEOUT: The request to https://dot.net/v1/dotnet-install.ps1 timed out at 600000 ms. This only occurs if your internet
 or the url are experiencing connection difficulties; not if the server is being slow to respond. Check your connection, the url, and or increase the timeout value here: https://github.com/dotnet/vscode-dotnet-runtime/blob/main/Documentation/troubleshooting-runtime.md#install-script-timeouts

Still downloading .NET version(s) 7.0.12~x64 ............................................................................................................

Further technical details

• Your VSCode Version
  1.83.1 (user setup)
• The version of the extension that's on your machine
  v1.8.1
• Your operating system details
  Windows 11 Enterprise

[JohnRCoder]

I'm getting what appears to be the exact same issue, for .NET 6.0; here's a dump of what its doing:

TelerikInc.blazortemplatewizard requested to download the .NET Runtime.
Downloading .NET version(s) 6.0.23~x64 ...................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... Error!
TIMEOUT: The request to https://dot.net/v1/dotnet-install.ps1 timed out at 600000 ms. This only occurs if your internet
or the url are experiencing connection difficulties; not if the server is being slow to respond. Check your connection, the url, and or increase the timeout value here: https://github.com/dotnet/vscode-dotnet-runtime/blob/main/Documentation/troubleshooting-runtime.md#install-script-timeouts

Still downloading .NET version(s) 6.0.23~x64 ...................................................................................................................................................................................................................................................................................................................................................................................................

This is happening with THIS version of Code:
Version: 1.83.1 (user setup)
Commit: f1b07bd25dfad64b0167beb15359ae573aecd2cc
Date: 2023-10-10T23:48:05.904Z
Electron: 25.8.4
ElectronBuildId: 24154031
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.19045

[nagilson]

There are hundreds of URLs we download from, but they all come from the same root domains.
https://dot.net, https://download.visualstudio.microsoft.com/, https://dotnetcli.blob.core.windows.net/, https://dotnetcli.azureedge.net, https://aka.ms/dotnet/.

Please let me know if this helps. Btw, if you are in China or India, the azureedge website doesn't work all too well. We are working with teams to try to fix that.

[JohnRCoder]

We’re in mainstream USA—NJ. Are you thinking one of the URLs below is being blocked? John Carling Director of Application Development Spectrotel<http://www.spectrotel.com/> P: 732.345.7863 ***@***.*** From: Noah Gilson ***@***.***> Sent: Monday, October 16, 2023 7:40 PM To: dotnet/vscode-dotnet-runtime ***@***.***> Cc: John Carling ***@***.***>; Manual ***@***.***> Subject: Re: [dotnet/vscode-dotnet-runtime] .NET Runtime update timeout (Issue #1463) There are hundreds of URLs we download from, but they all come from the same root domains. https://dot.net<https://dot.net>, https://download.visualstudio.microsoft.com/<https://download.visualstudio.microsoft.com>, https://dotnetcli.blob.core.windows.net/<https://dotnetcli.blob.core.windows.net>, https://dotnetcli.azureedge.net<https://dotnetcli.azureedge.net>, https://aka.ms/dotnet/<https://aka.ms/dotnet>. Please let me know if this helps. Btw, if you are in China or India, the azureedge website doesn't work all too well. We are working with teams to try to fix that. — Reply to this email directly, view it on GitHub<#1463 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABUZ5ZMF3KXHN5AR2BAHAV3X7XAUFAVCNFSM6AAAAAA56JH7ECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRVGQZTAMZSGM>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>

[nagilson]

Relevant thread, the entire network is different since this last post and is being updated again: dotnet/core#9677