Build Task Hangs when invoked from Solution Explorer

[isaacrlevin]

Type: Bug

• Install C# Dev Kit on VS Code Insiders
• Create new project (any will work)
• In Solution Explorer, right-click --> build project
• dotnet build task just hangs there, not completing

Extension version: 0.1.83
VS Code version: Code - Insiders 1.79.0-insider (aee52551e25d98391f9064996196cd83a9fc8669, 2023-06-06T15:00:13.166Z)
OS version: Windows_NT x64 10.0.25375
Modes:

System Info

Item	Value
CPUs	AMD Ryzen 5 3600 6-Core Processor (12 x 3600)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled
Load (avg)	undefined
Memory (System)	63.93GB (34.38GB free)
Process Argv	-n
Screen Reader	no
VM	0%

[isaacrlevin]

@timheuer VS Code doesn't seem to append setting/extension data into issues. Here is a gif of the issue. Not sure what you need to better triage

[timheuer]

Thanks Isaac -- per our side chat -- you were seeing this when you had a profile set as well right?

[isaacrlevin]

Nope it works totally fine on a "clean" version of VS Code Insiders. I assume there is some setting or Extension that is the issue here. Not a VS Code expert so not sure where to start, but more than happy to provide any logs or whatever you need.

[Michael-Eng]

@Erarndt can you investigate? I think we just invoke dotnet.exe to build?

[Erarndt]

@isaacrlevin , do you have any additional details about how I might be able to reproduce this issue? I've been trying to reproduce this with no success. The build process is rather simple since we just invoke dotnet.exe to build. You mentioned that it seems to be a setting or another extension that's contributing to this issue since a "clean" version doesn't exhibit this problem. If you disable the other extensions, in the problematic scenario, does the issue reproduce? You can disable extensions via the context menu in the Extensions view:

Happy to chat if you have any questions.