Discovery of bundled DotnetTools

Continue of this discussion

Should we add DotNetTools Command into help? And what does it look like

Current help text:

.NET Command Line Tools (2.1.300-preview2-008172)
Usage: dotnet [runtime-options] [path-to-application]
Usage: dotnet [sdk-options] [command] [arguments] [command-options]

path-to-application:
  The path to an application .dll file to execute.

SDK commands:
  new              Initialize .NET projects.
  restore          Restore dependencies specified in the .NET project.
  run              Compiles and immediately executes a .NET project.
  build            Builds a .NET project.
  publish          Publishes a .NET project for deployment (including the runtime).
  test             Runs unit tests using the test runner specified in the project.
  pack             Creates a NuGet package.
  migrate          Migrates a project.json based project to a msbuild based project.
  clean            Clean build output(s).
  sln              Modify solution (SLN) files.
  add              Add reference to the project.
  remove           Remove reference from the project.
  list             List reference in the project.
  nuget            Provides additional NuGet commands.
  msbuild          Runs Microsoft Build Engine (MSBuild).
  vstest           Runs Microsoft Test Execution Command Line Tool.
  store            Stores the specified assemblies in the runtime store.
  install          Installs an item into the development environment.
  uninstall        Uninstalls a tool from the development environment.
  help             Show help.

Common options:
  -v|--verbosity        Set the verbosity level of the command. Allowed values are q[uiet], m[inimal], n[ormal], d[etailed], and diag[nostic].
  -h|--help             Show help.

Run 'dotnet COMMAND --help' for more information on a command.

sdk-options:
  --version        Display .NET Core SDK version.
  --info           Display .NET Core information.
  --list-sdks      Display the installed SDKs.
  --list-runtimes  Display the installed runtimes.
  -d|--diagnostics Enable diagnostic output.

runtime-options:
  --additionalprobingpath <path>    Path containing probing policy and assemblies to probe for.
  --fx-version <version>            Version of the installed Shared Framework to use to run the application.
  --roll-forward-on-no-candidate-fx Roll forward on no candidate shared framework is enabled.
  --additional-deps <path>          Path to additional deps.json file.

[danroth27]

I think we should have a description for the additional commands. Proposed ordering is alphabetical Proposed descriptions:

dev-certs - Create and manage development certificates.
ef - Entity Framework Core command-line tools.
sql-cache - SQL Server cache command-line tools.
user-secrets - Manage development user secrets.

I don’t think we need the dotnet prefix for the additional commands.

We should still point to --help for additional details on these commands, but can we do that in a cross cutting way like we do for the SDK commands listed above? Similarly can we say that the dotnet blah pattern is still needed for these commands in a cross cutting way?

[danroth27]

My opinion on this is that it seems unfortunate to pollute the help text with tools that are highly specialized, like dev-certs and sql-cache. You want the most commonly used tools to be easy to find. I’m fine with the idea of having an “Additional commands” section.