Azure Trusted Signing & Code Signing Hooks

InstallAware has introduced future-proof Code Signing Hooks to ensure that no matter which new code signing vendor or standard emerges in the future, you shall be able to successfully sign your packages as a central part of your build process:

Run single or multiple command lines
Automatic invocation each time the IDE would normally sign a file, as determined normally by your project settings and code signing policy
Should any specified command line fail, your build would abort as would normally happen

InstallAware has also collected and documented common pitfalls encountered during the code signing process while implementing Azure Trusted Signing.

Best of all, when you employ Azure Trusted Signing, your projects receive instant trust from the operating system - a process that normally takes weeks (or months) with OV certificates, and is currently afforded only to EV certificates (which are themselves a huge roadblock to build automation due to physical code signing dongle presence requirements).

Last but not least, you may even skip SHA-1 code signing to speed up your builds.