emendelson Posted December 18, 2022 Share Posted December 18, 2022 In order to codesign a script while compiling it, it's possible to add a command to the Run After tab, but when I do this, I always have to switch manually to the box where Windows asks for permission to run the program. This is only an inconvenience, but other IDEs make the process smoother by including a built-in option to specify a code-sign command so that you don't have to switch focus and click a box. An example of this is InnoScript Studio for compiling InnoSetup installation scripts. Is there any hope that this could be include in ScITE in the future? I'm already so grateful for what ScITE does that I'm perfectly happy with what I have now, but I hope this might be a useful addition. Link to comment Share on other sites More sharing options...
steve8tch Posted January 10, 2023 Share Posted January 10, 2023 Yes - you can build this into the compile flow in Scite. Here is an example that we use #AutoIt3Wrapper_Run_After=c:\Windows\signtool.exe sign /sha1 <Your Certificate HASH> /t http://timestamp.comodoca.com "%out%" Hope this helps emendelson 1 Link to comment Share on other sites More sharing options...
emendelson Posted January 10, 2023 Author Share Posted January 10, 2023 (edited) @steve8tch That works perfectly. Thank you. Instead of running signtool.exe, directly in the Run After field, I had been using a compiled AutoIt executable that runs the signtool.exe command with the required parameters, and the workflow got interrupted by the prompt asking me to run the file. Your solution avoids the interruption. Thank you again. Edited January 10, 2023 by emendelson Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now