Skip to content

Tweak the wording on DOTNET_HOST_PATH docs to align with the new world #49422

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

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
+3 −8
Open

Tweak the wording on DOTNET_HOST_PATH docs to align with the new world #49422

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
8fd9568
Tweak the wording on DOTNET_HOST_PATH docs to align with the new world
baronfel Oct 22, 2025
3365d4e
Update docs/core/tools/dotnet-environment-variables.md
baronfel Oct 22, 2025
bad6ae6
Update docs/core/tools/dotnet-environment-variables.md
baronfel Oct 22, 2025
48bc2a8
Fix whitespace
baronfel Oct 22, 2025
4e1edd2
Update docs/core/tools/dotnet-environment-variables.md
baronfel Oct 22, 2025
1ca22f8
Update docs/core/tools/dotnet-environment-variables.md
baronfel Oct 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 3 additions & 8 deletions docs/core/tools/dotnet-environment-variables.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -183,15 +183,10 @@ These environment variables are used only when running apps via generated execut

### `DOTNET_HOST_PATH`

Specifies the absolute path to a `dotnet` host (`dotnet.exe` on Windows, `dotnet` on Linux and macOS) that was used to launch the currently-running `dotnet` process. This is used by the .NET SDK to help tools that run during .NET SDK commands ensure they use the same `dotnet` runtime for any child `dotnet` processes they create for the duration of the command. Tools and MSBuild Tasks within the SDK that invoke binaries via the `dotnet` host are expected to honor this environment variable to ensure a consistent experience.
Specifies the absolute path to a `dotnet` host (`dotnet.exe` on Windows, `dotnet` on Linux and macOS). This path represents either the host used to launch the currently running `dotnet` process, or the host that would be used when running `dotnet` commands for the currently building project when executing under MSBuild. The .NET SDK uses this variable to help tools that run during .NET SDK commands ensure they use the same `dotnet` host configuration for any child `dotnet` processes they create for the duration of the command. Tools and any MSBuild logic that run within a build and invoke binaries via the `dotnet` host are expected to honor this environment variable to ensure a consistent experience.

Tools that invoke `dotnet` during an SDK command should use the following algorithm to locate it:

- if `DOTNET_HOST_PATH` is set, use that value directly
- otherwise, rely on `dotnet` via the system's `PATH`

> [!NOTE]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Keep this. You cannot rely on DOTNET_HOST_PATH being set unless you were launched from the SDK

> `DOTNET_HOST_PATH` is not a general solution for locating the `dotnet` host. It is only intended to be used by tools that are invoked by the .NET SDK.
Starting in Visual Studio 2026, MSBuild in Visual Studio _also_ ensures that `DOTNET_HOST_PATH` is set for all builds of .NET SDK projects. For greatest consistency, all MSBuild tools and logic that want to use _the same dotnet binary_ as the one that spawned the build should rely on
`DOTNET_HOST_PATH` and should consider emitting a diagnostic (warning or error) when the variable is not present.

### `DOTNET_LAUNCH_PROFILE`

Expand Down