Brutal.Dev.StrongNameSigner 1.5.0

.NET Assembly Strong-Name Signer

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 is a newer version of this package available.
See the version list below for details.
Install-Package Brutal.Dev.StrongNameSigner -Version 1.5.0
dotnet add package Brutal.Dev.StrongNameSigner --version 1.5.0
<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
The NuGet Team does not provide support for this client. Please contact its maintainers for support.

Release Notes

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.


This package has no dependencies.

Version History

Version Downloads Last updated
2.3.0 7,177 8/29/2018
2.2.0 144 8/28/2018
2.1.4 4,501 1/18/2018
2.1.3 10,183 5/12/2017
2.1.2 483 5/1/2017
2.1.0 9,386 9/24/2016
1.8.0 7,775 5/5/2016
1.7.0 1,753 4/14/2016
1.6.1 2,894 1/7/2016
1.5.1 4,179 8/2/2015
1.5.0 830 7/4/2015
1.4.9 409 7/1/2015
1.4.8 676 5/30/2015
1.4.7 368 5/28/2015
1.4.6 348 5/28/2015
1.4.5 470 5/16/2015
1.4.4 372 4/30/2015
Show less