-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
replace cmd.exe usage with optional params for windows #128
Conversation
17aeccb
to
309ef2a
Compare
Released in alpha 1. |
@dtitenko @damianh @pawelros @leastprivilege please feel free to kick the tyres on this when you have time. Version is |
I tried it in IdentityModel https://github.com/IdentityModel/IdentityModel/blob/features/simpleExecTests/build/build.csproj works fine - both locally and on Azure Pipelines using the VS2017 image. Once I switch to the VS2019 image - I get https://dev.azure.com/netidentity/IdentityModel/_build/results?buildId=342 any idea? |
@leastprivilege no idea, but I got it to work by switching to I can only guess that something is borked with PowerShell on the new image. |
Any chance this can be added to the readme? I spent ages looking for workarounds before I found this PR. |
@robertcoltheart is this what you had in mind? #185 |
Reviewed, thanks! |
cmd.exe
is no longer used internally to execute commands on Windows.There are two new optional parameters,
windowsName
andwindowsArgs
. If either the command name or arguments need to be different on Windows, they can be specified as arguments to these parameters. For example: