-
Notifications
You must be signed in to change notification settings - Fork 347
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
"SignToolTasks.SignToolPath" can't find the correct path for signtool.exe #1186
Labels
Comments
gustavocalheiros
pushed a commit
to gustavocalheiros/nuke
that referenced
this issue
May 31, 2023
3 tasks
3 tasks
gustavocalheiros
pushed a commit
to gustavocalheiros/nuke
that referenced
this issue
Jun 28, 2023
gustavocalheiros
pushed a commit
to gustavocalheiros/nuke
that referenced
this issue
Apr 5, 2024
gustavocalheiros
pushed a commit
to gustavocalheiros/nuke
that referenced
this issue
Apr 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Usage Information
Nuke.Common 7.0.2 / Microsoft.NET 4.8.1 / Windows 10
Description
When trying to run "SignToolTasks.SignTool()", I have the following error:
"SignToolTasks.SignToolPath" looks for an old array of paths that don't correspond anymore with the latest windows kits released.
(current code: https://github.com/nuke-build/nuke/blob/develop/source/Nuke.Common/Tools/SignTool/SignToolSettings.cs)
For instance, I have "signtool.exe" installed on the path: "C:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\x64\signtool.exe" (and the env variable "SIGNTOOL_EXE" not set)
Reproduction Steps
Install any Windows Kit 10.*
Expected Behavior
signtool should work without problems
Actual Behavior
An exception is thrown
Regression?
No response
Known Workarounds
Set manually the env variable "SIGNTOOL_EXE" with the correct path.
Could you help with a pull-request?
Yes
The text was updated successfully, but these errors were encountered: