Developers often face challenges when it comes to integrating signing into their workflows. Microsoft’s Trusted Signing aims to simplify this process by integrating it into developer tools and CI/CD pipelines. This includes tools like Windows SDK SignTool.exe, the Trusted Signing Azure DevOps Extension, and the Trusted Signing GitHub Action.
During the Trusted Signing Preview, developers shared various solution patterns and supported each other in the community. This collaboration led to simplifications in signing solutions, saving time and allowing developers to focus on other tasks. Some solutions, like the Trusted Signing Client Tools Installer and dotnet/sign integration, were released for all subscribers to use.
The Trusted Signing Client Tools Installer simplifies the setup of Windows SDK SignTool.exe and its dependencies. It can be easily installed using PowerShell commands or WinGet. The dotnet/sign CLI tool also supports Trusted Signing for signing operations, like NuGet packages and ClickOnce deployments.
Additionally, Advanced Installer now offers Trusted Signing integration, allowing developers to sign their binaries and packaging projects in one step. This integration has helped projects like ImageMagick streamline their signing process and modernize their installers.
Trusted Signing subscribers have also shared their own solutions, like Jsign for Authenticode signing in Java, KoalaDocs for plugin developers
