Automatic strong-name signing of referenced assemblies.
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.
Install-Package Brutal.Dev.StrongNameSigner -Version 2.7.1
dotnet add package Brutal.Dev.StrongNameSigner --version 2.7.1
<PackageReference Include="Brutal.Dev.StrongNameSigner" Version="2.7.1" />
paket add Brutal.Dev.StrongNameSigner --version 2.7.1
#r "nuget: Brutal.Dev.StrongNameSigner, 2.7.1"
- Improved performance of automated build task by ignoring checks against SDK and standard library assemblies that will/should always be signed anyway (Issue #57).
- Improved errors when files are not found.
- Log with high priority when files are being changed during the automated signing process.
This package has no dependencies.
NuGet packages (1)
Showing the top 1 NuGet packages that depend on Brutal.Dev.StrongNameSigner:
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:
WireMock.Net is a flexible library for stubbing and mocking web HTTP responses using request matching and response templating. Based on the functionality from http://WireMock.org, but extended with more functionality.
A turn-key library for building RESTful services
.Net library for TOML