Unix-like platforms (Linux, macOS): `System.Diagnostics.ProcessStartInfo`: Clarify the helper-utility based behavior of `UseShellExecute = true`

[mklement0]

As of this writing, https://learn.microsoft.com/en-US/dotnet/api/system.diagnostics.processstartinfo.useshellexecute is missing the following information:

• On Unix-like platforms, setting UseShellExecute to true requires external helper utilities to function:

  • On Linux: any one of the following three utilities must be locatable via the PATH environment variable: xdg-open, gnome-open or kfmclient

    • A given Linux distro may or may not come with any of these.

  • On macOS, the built-in open utility is called via its full path, /usr/bin/open

Generally, setting UseShellExecute to true is a GUI shell operation, and therefore makes no sense on terminal-only/headless systems.

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

Issue Details

---

As of this writing, https://learn.microsoft.com/en-US/dotnet/api/system.diagnostics.processstartinfo.useshellexecute is missing the following information:

• On Unix-like platforms, setting UseShellExecute to true requires external helper utilities to function:

  • On Linux: any one of the following three utilities must be locatable via the PATH environment variable: xdg-open, gnome-open or kfmclient

    • A given Linux distro may or may not come with any of these.

  • On macOS, the built-in open utility is called via its full path, /usr/bin/open

Generally, setting UseShellExecute to true is a GUI shell operation, and therefore makes no sense on terminal-only/headless systems.

Author:	mklement0
Assignees:	-
Labels:	untriaged, Pri3, area-System.Diagnostics
Milestone:	-