Gekka.MSBuild.targets.SignTool 0.2.9150.31270

dotnet add package Gekka.MSBuild.targets.SignTool --version 0.2.9150.31270
                    
NuGet\Install-Package Gekka.MSBuild.targets.SignTool -Version 0.2.9150.31270
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Gekka.MSBuild.targets.SignTool" Version="0.2.9150.31270" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Gekka.MSBuild.targets.SignTool" Version="0.2.9150.31270" />
                    
Directory.Packages.props
<PackageReference Include="Gekka.MSBuild.targets.SignTool" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Gekka.MSBuild.targets.SignTool --version 0.2.9150.31270
                    
#r "nuget: Gekka.MSBuild.targets.SignTool, 0.2.9150.31270"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#addin nuget:?package=Gekka.MSBuild.targets.SignTool&version=0.2.9150.31270
                    
Install Gekka.MSBuild.targets.SignTool as a Cake Addin
#tool nuget:?package=Gekka.MSBuild.targets.SignTool&version=0.2.9150.31270
                    
Install Gekka.MSBuild.targets.SignTool as a Cake Tool

MSBuildSignTool

Summary

Insert msbuild task to project for add sign to output files at Release build using signtool.exe.

This targets can sign to output file and publish file.

Feature

  • Search signtool.exe automticaly
  • Sign using pfx file and password.
  • Sign using Azure Trust Signing.
  • Sign in Github Actions.
  • Support Dual sign (SHA1 + SHA256).

Requirement

The signtool.exe must be installed, e.g., with the Windows SDK.
It must be possible to reference signtool from the developer command prompt.

If sign using Azure Trust Signing , need install Microsoft.Trusted.Signing.Client

Optional settings in project file

You can change the settings by adding them in the project file.

<Project >
    <PropertyGroup>
        <SignTool_TimeStampServer></SignTool_TimeStampServer>
        <SignTool_Algorithm_SHA1>false</SignTool_Algorithm_SHA1>
        <SignTool_Algorithm_SHA256>true</SignTool_Algorithm_SHA256>
        <SignTool_ExePath>path to signtool.exe</SignTool_ExePath>

        
        <SignTool_PFX      ></SignTool_PFX>
        <SignTool_Password ></SignTool_Password>

        
        <SignTool_Dlib_Dll_Path ></SignTool_Dlib_Dll_Path>
        <SignTool_Dlib_MetaJson_Path Condition></SignTool_Dlib_MetaJson_Path Condition>

        
        <SignTool_Nupkg_FingerPrint></SignTool_Nupkg_FingerPrint>
        <SignTool_Nupkg_SubjectName></SignTool_Nupkg_SubjectName>
        <SignTool_Nupkg_StoreName></SignTool_Nupkg_StoreName>
        <SignTool_Nupkg_StoreLocation></SignTool_Nupkg_StoreLocation>
        <SignTool_Nupkg_Pfx_Path></SignTool_Nupkg_Pfx_Path>
        <SignTool_Nupkg_Password></SignTool_Nupkg_Password>
    </PropertyGroup>

    <ItemDefinitionGroup>
        <SignTool_InputFiles Include="filepath1" />
        <SignTool_InputFiles Include="filepath2" />
    </ItemDefinitionGroup>

    <Target Name="Your Target Name" BeforeTargets="Build" >
        <ItemDefinitionGroup>
            <SignTool_InputFiles Include="filepath3" />
            <SignTool_InputFiles Include="filepath4" />
        </ItemDefinitionGroup>
    </Target>
  • SignTool_ExePath
    Path to use signtool.exe in any location If not set, use signtool.exe which can be referenced at developer command prompt

  • SignTool_TimeStampServer
    Url for timestamps server If not set, targets uses digicert's server.

  • SignTool_Algorithm_SHA1
    If set to true, sign with SHA1

  • SignTool_Algorithm_SHA256
    If set to true, sign with SHA256

    This target sign multiple signatures to one file if SHA1 and SHA256 are enabled.

  • SignTool_InputFiles
    If there are additional files to be signed, specify the path in Incldue.

    If the files does not exist before the project file is evaluated, it must be specified in custom target executed before the build

Supporting file types

Multi signable

  • .exe
  • .dll
  • .ocx
  • .scr
  • .sys
  • .cab
  • .cat
  • .efi

Only one of SHA1 or SHA256

  • .msi
  • .ps1
  • .vbs
  • .vbe
  • .js (JScript)

Only SHA256

  • .msix
  • .msixbundle
  • .appx
  • .appxbundle
There are no supported framework assets in this package.

Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
0.2.9150.31270 117 1/19/2025