[sdk 6.0.100-preview.1.21107.2-win-x64] dotnet tool fail due to argument passed to the tool.

The cli tries to parse the ‘-v’ argument that is passed to the tool, previously the cli ignored this argument.

25>System.InvalidOperationException: Cannot parse argument 'Release' as expected type Microsoft.DotNet.Cli.VerbosityOptions.
25>   at System.CommandLine.Binding.ArgumentConverter.GetValueOrDefault[T](ArgumentConversionResult result)
25>   at System.CommandLine.Parsing.OptionResultExtensions.GetValueOrDefault[T](OptionResult optionResult)
25>   at System.CommandLine.Parsing.ParseResult.ValueForOption[T](String alias)
25>   at Microsoft.DotNet.Cli.Telemetry.TelemetryFilter.LogVerbosityForAllTopLevelCommand(ICollection`1 result, ParseResult parseResult, String topLevelCommandName)
25>   at Microsoft.DotNet.Cli.Telemetry.TelemetryFilter.Filter(Object objectToFilter)
25>   at Microsoft.DotNet.Cli.Utils.TelemetryEventEntry.SendFiltered(Object o)
25>   at Microsoft.DotNet.Cli.Program.ProcessArgs(String[] args, ITelemetry telemetryClient)
25>   at Microsoft.DotNet.Cli.Program.Main(String[] args)
25>C:\dev\Opal\CKSetup\CKSetup.csproj(12,5): error MSB3073: The command "dotnet cksetup run CKSetup.xml -v Release --logFile LastRun.log" exited with code 1.

I believe this is a regression from .NET 5.

[dsplaisted]

@sfoslund This looks like an issue with the new command line parser

[sfoslund]

Oh I see, it’s not reproducing for me when run globally but it does locally. It does seem to be a parser issue, I’ll look into this.