Is your feature request related to a problem? Please describe.
I want to use dotnet sign to batch sign files when using velopack installer.
That means that it must support multiple files one after each other on the command prompt (space separated)
Based on the current helt sign code azure-key-vault <file(s)> [options] i expected that I could just specify several files after each other, but it does not work and I get Unrecognized command or argument '"file2.exe"'. when I specify more that 1 file
Describe the solution you'd like
A clear and concise description of what you want to happen.
I want to be able to call dotnet sign using the following syntax
sign code azure-key-vault "file1" "file2.exe" "file3.exe" --option1sign code azure-key-vault --option1 file1 file 2 file3
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
don't do batch signing, use another tool
Additional context
Include the output of sign --version.
Add any other context about the problem here.
Is your feature request related to a problem? Please describe.
I want to use
dotnet sign
to batch sign files when usingvelopack
installer. That means that it must support multiple files one after each other on the command prompt (space separated)Based on the current helt
sign code azure-key-vault <file(s)> [options]
i expected that I could just specify several files after each other, but it does not work and I getUnrecognized command or argument '"file2.exe"'.
when I specify more that 1 fileDescribe the solution you'd like A clear and concise description of what you want to happen.
I want to be able to call dotnet sign using the following syntax
sign code azure-key-vault "file1" "file2.exe" "file3.exe" --option1
sign code azure-key-vault --option1 file1 file 2 file3
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
don't do batch signing, use another tool
Additional context Include the output of sign --version. Add any other context about the problem here.
It seems dotnet sign uses System.CommandLine? if so then according to the documentation it might be possible to set Option.AllowMultipleArgumentsPerToken to true for the files argument.