Brutal.Dev.StrongNameSigner 3.3.3

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


                    

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


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="Brutal.Dev.StrongNameSigner" />
                    


                            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 Brutal.Dev.StrongNameSigner --version 3.3.3
                    


                    

                
#r "nuget: Brutal.Dev.StrongNameSigner, 3.3.3"
#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. 
#:package [email protected]
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=Brutal.Dev.StrongNameSigner&version=3.3.3
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=Brutal.Dev.StrongNameSigner&version=3.3.3
                    


                            Install as a Cake Tool

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.

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 (2)

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

Repository Stars
fluentmigrator/fluentmigrator
Fluent migrations framework for .NET
paiden/Nett
.Net library for TOML
Version Downloads Last Updated
3.7.1 1,707 5/9/2026
3.7.0 167 5/8/2026
3.6.5 692 3/11/2026
3.6.4 10,268 2/17/2026
3.6.3 6,614 9/8/2025
3.6.2 294 9/1/2025
3.6.1 837 7/22/2025
3.5.1 7,141 3/30/2025
3.5.0 65,161 2/5/2024
3.4.0 4,495 10/23/2023
3.3.3 32,628 1/21/2023
3.3.2 2,144 1/12/2023
3.3.1 2,014 1/10/2023
3.2.1 1,783 12/19/2022
3.2.0 1,822 12/16/2022
3.1.1 2,198 10/17/2022
3.1.0 95,518 12/30/2021
Loading failed

Fix #86 - Generic error handling to continue processing files that cause unusual errors.
Fix #89 - Ignore copy/overwrite failures if files are locked.
Fix #90 - Change the name of the "Signed" column to "Strong-named" to avoid confusion.
Fix #92 - Ignore custom attribute errors when it comes to assembly resolution.