Brutal.Dev.StrongNameSigner 1.5.0

There is a newer version of this package available.
See the version list below for details. 
dotnet add package Brutal.Dev.StrongNameSigner --version 1.5.0                

                    
                

            
NuGet\Install-Package Brutal.Dev.StrongNameSigner -Version 1.5.0
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="Brutal.Dev.StrongNameSigner" Version="1.5.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add Brutal.Dev.StrongNameSigner --version 1.5.0                

                    
                

            
#r "nuget: Brutal.Dev.StrongNameSigner, 1.5.0"
#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. 
// Install Brutal.Dev.StrongNameSigner as a Cake Addin
#addin nuget:?package=Brutal.Dev.StrongNameSigner&version=1.5.0

// Install Brutal.Dev.StrongNameSigner as a Cake Tool
#tool nuget:?package=Brutal.Dev.StrongNameSigner&version=1.5.0

Utility software to strong-name sign .NET assemblies, including assemblies you do not have the source code for.

If you strong-name sign your own projects you may have noticed that if you reference an unsigned third party assembly you get an error similar to "Referenced assembly 'A.B.C' does not have a strong name". If you did not create this assembly, you can use this tool to sign the assembly with your own (or temporarily generated) strong-name key.

The tool will also re-write the assembly references (as well as any InternalsVisibleTo references) to match the new signed versions of the assemblies you create.

There are no supported framework assets in this package.

Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on Brutal.Dev.StrongNameSigner:

Package Downloads
Atlassian.SDK.Signed

Utilities to interact with Atlassian products. Contains LinqToJira provider for querying JIRA Issue tracker (http://www.atlassian.com/software/jira).

GitHub repositories (3)

Showing the top 3 popular GitHub repositories that depend on Brutal.Dev.StrongNameSigner:

Repository Stars
fluentmigrator/fluentmigrator
Fluent migrations framework for .NET
WireMock-Net/WireMock.Net
WireMock.Net is a flexible product for stubbing and mocking web HTTP responses using advanced request matching and response templating. Based on the functionality from http://WireMock.org, but extended with more functionality.
paiden/Nett
.Net library for TOML
Version Downloads Last updated
3.5.0 17,772 2/5/2024
3.4.0 4,024 10/23/2023
3.3.3 19,588 1/21/2023
3.3.2 1,926 1/12/2023
3.3.1 1,818 1/10/2023
3.2.1 1,565 12/19/2022
3.2.0 1,600 12/16/2022
3.1.1 1,953 10/17/2022
3.1.0 85,897 12/30/2021
3.0.5-beta 1,485 12/8/2021
2.9.1 12,579 11/16/2021
2.9.0 2,690 11/2/2021
2.8.0 10,576 5/10/2021
2.7.1 103,847 12/12/2019
2.6.0 3,879 11/25/2019
2.4.0 2,891 9/18/2019
2.3.0 25,238 8/29/2018
2.2.0 1,891 8/28/2018
2.1.4 17,460 1/18/2018
2.1.3 34,048 5/12/2017
2.1.2 2,525 5/1/2017
2.1.0 26,827 9/24/2016
1.8.0 18,503 5/5/2016
1.7.0 7,827 4/14/2016
1.6.1 5,708 1/7/2016
1.5.1 12,648 8/2/2015
1.5.0 3,417 7/4/2015
1.4.9 2,698 7/1/2015
1.4.8 3,575 5/30/2015
1.4.7 2,437 5/28/2015
1.4.6 2,438 5/28/2015
1.4.5 2,854 5/16/2015
1.4.4 3,016 4/30/2015

Cache generated strong-name keys to ensure all assemblies are signed with the same key pair. This ensure they are not invalidated when references are fixed and they get re-signed.

Fix odd issue with ClickOnce deployments failing signature checks when caching the strong-name key object.