Skip to content

dotnet help still lists -v | --verbose as an option #7621

Closed

Description

@eerhardt

Steps to reproduce

dotnet help

Expected behavior

There shouldn't be a --verbose flag listed

Actual behavior

Erics-MBP:Foundatio eerhardt$ dotnet help
.NET Command Line Tools (1.0.0-rc3-004530)
Usage: dotnet [host-options] [command] [arguments] [common-options]

Arguments:
  [command]             The command to execute
  [arguments]           Arguments to pass to the command
  [host-options]        Options specific to dotnet (host)
  [common-options]      Options common to all commands

Common options:
  -v|--verbose          Enable verbose output
  -h|--help             Show help 

Environment data

dotnet --info output:

Erics-MBP:Foundatio eerhardt$ dotnet --info
.NET Command Line Tools (1.0.0-rc3-004530)

Product Information:
 Version:            1.0.0-rc3-004530
 Commit SHA-1 hash:  0de3338607

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.12
 OS Platform: Darwin
 RID:         osx.10.12-x64
 Base Path:   /usr/local/share/dotnet/sdk/1.0.0-rc3-004530

Activity

  1. TheRealPiotrP commented on Jan 30, 2017

    @TheRealPiotrP

    ok... I'll bite :) why should we remove this from --help?

  2. eerhardt commented on Jan 30, 2017

    @eerhardt
    MemberAuthor

    ok... I'll bite :) why should we remove this from --help?

    because it is incorrect.

  3. eerhardt commented on Jan 30, 2017

    @eerhardt
    MemberAuthor
  4. TheRealPiotrP commented on Jan 31, 2017

    @TheRealPiotrP

    it's wrong in [host options]...

  5. livarcocc commented on Jan 31, 2017

    @livarcocc
    Contributor

    No, it is correct. Now, the format is dotnet -d new. But this one is also correct. All commands (most of them) support verbose, so that you can do dotnet run --verbose.

  6. livarcocc commented on Jan 31, 2017

    @livarcocc
    Contributor

    not that -d is for the diagnostics of the CLI, like verbosity for tools messages, etc. Whatever goes to Reporter.Verbose, while --verbose is for msbuild verbosity.

  7. eerhardt commented on Jan 31, 2017

    @eerhardt
    MemberAuthor
    F:\DotNetTest\Hoist\App>dotnet build --verbose
    Microsoft (R) Build Engine version 15.1.523.56541
    Copyright (C) Microsoft Corporation. All rights reserved.
    
    MSBUILD : error MSB1001: Unknown switch.
    Switch: --verbose
    
    For switch syntax, type "MSBuild /help"
    
  8. TheRealPiotrP commented on Feb 1, 2017

    @TheRealPiotrP

    @jonsequitur is starting to look at some post-1.0 work to help ensure consistency across commands.

    The bug here is that the 'msbuild' commands dropped support for --verbose and the text mismatches reality. The fix here will need to wait for the next release. @blackdwarf do you have a design for how we should unify --verbose with --verbosity?

  9. MiKom commented on Feb 2, 2017

    @MiKom

    I'd like to point out that this breaks "dotnet restore" in Visual Studio Code.

  10. thesmithee commented on Feb 2, 2017

    @thesmithee

    @piotrpMSFT we have renamed the --verbose option to --diagnostic I believe. With this, there is no unification I can see that is needed. We should rename it and potentially re-arrange the help screen to be more intuitive.

    @MiKom can you provide more details? I'm not sure what is breaking dotnet restore in VS Code, since AFAIR VS Code does not invoke restore with any special verbosity levels.

  11. MiKom commented on Feb 2, 2017

    @MiKom

    @blackdwarf Sorry for confusion. I was testing it on VS Code 1.8. After upgrade to 1.9 it behaves differently.

    I made new web1.1 project via "dotnet new -t web1.1" in powershell without problems. Then I've opened the folder in VS Code 1.9 with C# extension and got this:

    Starting OmniSharp server at 2.02.2017, 20:05:20
        Target: c:\Users\mikom\Documents\asp_tests\asp11
    
    OmniSharp server started
        Path: C:\Users\mikom\.vscode\extensions\ms-vscode.csharp-1.6.2\bin\omnisharp\OmniSharp.exe
        PID: 11088
    
    OmniSharp: -s c:\Users\mikom\Documents\asp_tests\asp11 --hostPID 16284 --stdio DotNet:enablePackageRestore=false --encoding utf-8 formattingOptions:useTabs=false formattingOptions:tabSize=4 formattingOptions:indentationSize=4
    [INFORMATION:OmniSharp.Startup] Omnisharp server running using Stdio at location 'c:\Users\mikom\Documents\asp_tests\asp11' on host 16284.
    [INFORMATION:OmniSharp.DotNet.DotNetProjectSystem] Initializing in c:\Users\mikom\Documents\asp_tests\asp11
    [INFORMATION:OmniSharp.DotNet.DotNetProjectSystem] Auto package restore: False
    [INFORMATION:OmniSharp.DotNet.DotNetProjectSystem] Update workspace context
    [INFORMATION:OmniSharp.DotNet.DotNetProjectSystem] Resolving projects references
    [INFORMATION:OmniSharp#MSBuild] MSBUILD_EXE_PATH environment variable set to C:\Users\mikom\.vscode\extensions\ms-vscode.csharp-1.6.2\bin\omnisharp\msbuild\MSBuild.exe
    [INFORMATION:OmniSharp#MSBuild] MSBuildExtensionsPath environment variable set to C:\Users\mikom\.vscode\extensions\ms-vscode.csharp-1.6.2\bin\omnisharp\msbuild
    [INFORMATION:OmniSharp#MSBuild] MSBuildSDKsPath environment variable set to C:\Users\mikom\.vscode\extensions\ms-vscode.csharp-1.6.2\bin\omnisharp\msbuild\Sdks
    [INFORMATION:OmniSharp#MSBuild] No solution files found in 'c:\Users\mikom\Documents\asp_tests\asp11'
    [INFORMATION:OmniSharp#MSBuild] Add project: c:\Users\mikom\Documents\asp_tests\asp11\asp11.csproj
    [INFORMATION:OmniSharp#MSBuild] Update project: asp11
    [INFORMATION:OmniSharp.Script.ScriptProjectSystem] Detecting CSX files in 'c:\Users\mikom\Documents\asp_tests\asp11'.
    [INFORMATION:OmniSharp.Script.ScriptProjectSystem] Could not find any CSX files
    [INFORMATION:OmniSharp.Startup] Configuration finished.
    
  12. self-assigned this
    on May 19, 2017
  13. transferred this issue fromdotnet/clion Jan 31, 2020
  14. added this to the 2.0.0 milestone on Jan 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions