Initializing MSBuild project tools runs forever

[TomSwiedler]

When starting VSCode the Initializing MSBuil project tools runs forever trying to download DOTNET CORE 8.0.

DOTNET CORE 8.0.2 is already installed.

DOTNET --info: .NET SDK: Version: 8.0.200 Commit: 438cab6a9d Workload version: 8.0.200-manifests.e2473a36

Runtime Environment: OS Name: Windows OS Version: 10.0.19045 OS Platform: Windows RID: win-x64 Base Path: C:\dev\dotnet\sdk\8.0.200\

.NET workloads installed: There are no installed workloads to display.

Host: Version: 8.0.2 Architecture: x64 Commit: 1381d5ebd2

.NET SDKs installed: 6.0.407 [C:\dev\dotnet\sdk] 7.0.404 [C:\dev\dotnet\sdk] 8.0.100 [C:\dev\dotnet\sdk] 8.0.200 [C:\dev\dotnet\sdk]

.NET runtimes installed: Microsoft.AspNetCore.App 6.0.15 [C:\dev\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 7.0.14 [C:\dev\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 8.0.0 [C:\dev\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 8.0.1 [C:\dev\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 8.0.2 [C:\dev\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 6.0.15 [C:\dev\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 7.0.14 [C:\dev\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 8.0.0 [C:\dev\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 8.0.1 [C:\dev\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 8.0.2 [C:\dev\dotnet\shared\Microsoft.NETCore.App] Microsoft.WindowsDesktop.App 6.0.15 [C:\dev\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 7.0.14 [C:\dev\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 8.0.0 [C:\dev\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 8.0.2 [C:\dev\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found: None

Environment variables: DOTNET_ROOT [C:\dev\dotnet]

global.json file: Not found

Learn more: https://aka.ms/dotnet/info

Download .NET: https://aka.ms/dotnet/download

[tintoy]

Hi - are you able to post the log from the output window where it talks about trying to download .net 8?

[TomSwiedler]

tintoy.msbuild-project-tools requested to download the .NET Runtime. Downloading .NET version(s) 8.0.2~x64 ........................................................................................

The dots go on forever

[tintoy]

Hmm - that’s odd; I’ll see if I can figure out how to get the .net acquisition extension to log more extensively…

[tintoy]

Sorry for the delay, work’s been a little full-on this week.

Are you able to try the steps linked below to point it at your existing dotnet installation? I’d like to see if the problem is with detection or download…

https://github.com/dotnet/vscode-dotnet-runtime/blob/main/vscode-dotnet-runtime-extension/README.md#i-already-have-a-net-runtime-or-sdk-installed-and-i-want-to-use-it

This extension has the Id tintoy.msbuild-project-tools.

[TomSwiedler]

tintoy.msbuild-project-tools requested to download the .NET Runtime. Using configured .NET path: C:\dev\dotnet\dotnet.exe

[tintoy]

And does it still do the dots forever?

[lonix1]

In my case it downloaded in a previous session successfully.

But when I open vscode now, it shows that message forever, without trying to download anything (because that was already done). The workaround is to close and reopen.

(BTW I'm still using v7, but the extension is on v8 - is that a problem?)

[tintoy]

I wouldn’t have thought so; I’m still trying to reproduce the issue but I’ll try setting up a container tomorrow morning and see if I can get it to happen…

[TomSwiedler]

It did not attempt to download again for me

[tintoy]

I’m going to have another try tonight at reproducing this locally (sorry for the delay; I’ve been away on vacation) 🙂

[tintoy]

Hi - I've spent a couple of days trying to reproduce this behaviour but have been unable to (at least with the currently-released version of the extension).

Is anyone still experiencing the problem described in this issue?

[lonix1]

I haven't seen this problem again. (But don't recall there being any upgrades recently, so can't be sure.)

[TomSwiedler]

I removed the configuration for the extension from the settings.json file and it appears to still be loading properly.

[tintoy]

Great! Thanks for checking 🙂

I’m going to close this issue for now, but feel free to reopen it if the problem reoccurs.