You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
dotnet help still lists -v | --verbose as an option #7621
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
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.
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.
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"
@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?
@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.
@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.
Activity
TheRealPiotrP commentedon Jan 30, 2017
ok... I'll bite :) why should we remove this from --help?
eerhardt commentedon Jan 30, 2017
because it is incorrect.
eerhardt commentedon Jan 30, 2017
See dotnet/cli#5043
TheRealPiotrP commentedon Jan 31, 2017
it's wrong in [host options]...
livarcocc commentedon Jan 31, 2017
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.livarcocc commentedon Jan 31, 2017
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.
eerhardt commentedon Jan 31, 2017
TheRealPiotrP commentedon Feb 1, 2017
@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
--verboseand 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?MiKom commentedon Feb 2, 2017
I'd like to point out that this breaks "dotnet restore" in Visual Studio Code.
thesmithee commentedon Feb 2, 2017
@piotrpMSFT we have renamed the
--verboseoption to--diagnosticI 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 restorein VS Code, since AFAIR VS Code does not invoke restore with any special verbosity levels.MiKom commentedon Feb 2, 2017
@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: