[NETSDKE2E][v11][Linux][MAC] .NET SDK installed via Tooling Requirements could not be located by C#.

[vwenchen]

Regression Info

No regression info since it's new feature from this build.

Describe the issue

.NET SDK can't be found on the path after installing sdk using Tooling Requirements.

Collect logs

csdevkit-logs-2026-09-08T05-28-12.zip

Steps to reproduce

1. Clean machine: Linux/Mac
2. Install VS Code Insider - 1.137.0 and csdevkit-win32-arm64-9.9.510-ge32b16.vsix
3. Create a new Folder
4. Open it in VSCode
5. F1-> C#: Check Health-> install .NET10 SDK from Tooling Requirements
6. Click reload window
7. F1-> .NET: New Project ->Console App

Expected behavior

.NET SDK can be found on the path.

Actual behavior

.NET SDK can't be found on the path

Workaround

After set PATH manually, dotnet can be found.

[vwenchen]

Dotnetup also don't been added to PATH automatically when installing sdk using Tooling Requirements.

[JakeRadMSFT]

Finding: separate investigation; final-head validation is pending.

The original evidence points to a managed-host consumption problem after Tooling Requirements installs the SDK on a clean macOS/Linux machine: after Reload Window, .NET: New Project still cannot find dotnet, while manually updating PATH works.

In native macOS exploratory validation on a prior PR head, New Project worked without dotnet on the launch PATH and without mutating PATH; it consumed the selected managed host directly. Final-head validation is still pending, and that result does not prove the original Linux/macOS install-state failure is resolved.

vs-green PR !779247 does not currently claim to fix this issue.

Cowritten with Copilot

[NicoleWang001]

With the latest C# Dev Kit 11.0.26, the installed .NET SDK was not added to PATH, and was recognized by C# Doctor.

But could not be located by C# even re-open VSCode