When rolling out a Vista compatible installation file, I need to sign every executable (EXE and DLL) with my authenticode signature. Doing so involves executing the
signcode tool numerous times (for version 2.8.0 of Creative Docs .NET, this tool is invoked more than 30 times). And every time, I have to type in a pass phrase to validate the signature:

Maybe there is a solution to avoid having this dialog pop up 30 times, but I have not been able to find out how to do so. [Note: that's no longer true, read
here]
I finally decided to use a macro recorder to automate this part of the build: whenever the dialog pops up, a small utility called
PTFBPro awakes and sends the key strokes followed by
return to validate the private key... PTFBPro is well worth its $29.99!

In a previous blog post I presented my solution for automated code signing, which relied on PTFBPro to generate the necessary key strokes when the Enter Private Key Password window would pop up. A reader proposed another solution, which is cleaner: usi
Tracked: Mar 15, 10:31