Usage root command does not display `ToolCommandName` about command-line-api HOT 1 OPEN

I wonder if it would be possible to change .NET Runtime to use the original argv[0] of the process as Environment.GetCommandLineArgs()[0]. According to the documentation, "The first element is the executable file name", which does not promise that the string would always include a directory path. IIRC, on Windows, the Service Control Manager can place the service name there; and on GNU/Linux, argv[0] could have a - prefix if the application is being used as a login shell. It would be good to let the application read this information.

However, because .NET Core 1.0 already set the assembly path as the first array element, there must now be applications that expect it to keep working that way. Perhaps then, the safest fix would be to add new Environment.ProcessInvocationName API as an alternative of the existing Environment.ProcessPath. Related issues: dotnet/runtime#30212, dotnet/runtime#11305.

from command-line-api.