Jonathan Dodds

Thanks @baronfel. That's great news.

The `/etc/paths.d/` directory and the `dotnet-cli-tools` file are global for all users. Writing the full path of a specific user in this file should not be done.

The root issue is that "global" tools are not installed globally. They are installed only for a specific user. If the global tools were installed in a folder under `/usr/local/share/dotnet`,...

macOS is a multi-user operating system. I use fast user switching with family members. My son took a course that used C# and Unity. For me, although rare, it's not...

> @jrdodds So, you're saying if they allowed for a `user` scope for dotnet tools, adding further complexity, that would be better than fixing it for a vast majority of...

For `dotnet tool`, the "global" scope is the scope of a specific user. It does not mean global to all users. It means global to all projects for a specific...

I very strongly agree with: > When you're working on different platforms, you have to take the conventions of the platforms into account. For many *nix developers, both on Linux...

> it's tiresome to keep telling macOS folks to change that file on every SDK update. @cicorias Are you telling people to change the `/etc/paths.d/dotnet-cli-tools` file? For zsh, the following...

The change in PR #8710 was for BUG #8798

Hi @YuliiaKovalova, The tests still fail. The log files are attached. [Microsoft.Build.BuildCheck.UnitTests_net8.0_x64.zip](https://github.com/user-attachments/files/15551469/Microsoft.Build.BuildCheck.UnitTests_net8.0_x64.zip) MSBuild version 17.11.0-dev-24304-01+db79545e5 for .NET 17.11.0.3040 macOS Sonoma 14.5 Apple M1 Pro (ARM)