[Tools] The command name in installer message is confusingly

wcoder commented 6 years ago

From dotnet-outdated issue: https://github.com/jerriep/dotnet-outdated/issues/37

Steps to reproduce

Execute dotnet tool install --global dotnet-outdated

Expected behavior

So that the installer's messages are understood (the same command names).

Actual behavior

After success install:
dotnet-outdated - command not found, because used command dotnet outdated

Environment data

dotnet --info output:

.NET Core SDK (reflecting any global.json):
 Version:   2.1.301
 Commit:    59524873d6

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.13
 OS Platform: Darwin
 RID:         osx.10.13-x64
 Base Path:   /usr/local/share/dotnet/sdk/2.1.301/

Host (useful for support):
  Version: 2.1.1
  Commit:  6985b9f684

.NET Core SDKs installed:
  2.0.0 [/usr/local/share/dotnet/sdk]
  2.1.4 [/usr/local/share/dotnet/sdk]
  2.1.300-preview1-008174 [/usr/local/share/dotnet/sdk]
  2.1.301 [/usr/local/share/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.0-preview1-final [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.1 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.0-preview1-final [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.1 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 1.1.2 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.0 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.5 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.0-preview1-26216-03 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.1 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

peterhuene commented 6 years ago

@wli3 do you know of an issue this might be a dupe of? I couldn't find an issue that specifically requested turning dotnet- prefixed global tools to dotnet <command> in the install output, although I thought we had one. If not, let's take this for 2.2.100.

wli3 commented 6 years ago

I think there is 2 problem.

@wcoder dotnet-outdated should work after reopen cmd. Since the message about HTTPS cert shows up. I guess this is the first run. If there is no message about reopen cmd prompt in the first run, it is a bug.
I don't think there is an existing issue to simply "dotnet-outdated" to "dotnet outdated" in the message.

dotnet / sdk