A utility to strong-name sign .NET assemblies, including third-party libraries without source code, and fix their references.
StrongNameSigner is a utility tool for .NET developers that strong-name signs assemblies, including third-party libraries for which source code is unavailable. It addresses the common compilation error 'Referenced assembly does not have a strong name' by signing these assemblies and automatically fixing their references to ensure compatibility in strong-named projects.
.NET developers and teams who need to strong-name sign their projects but rely on unsigned third-party NuGet packages or libraries, particularly those working in enterprise environments with strict assembly signing requirements.
Developers choose StrongNameSigner because it provides a reliable, automated solution to sign and fix references across complex dependency chains without requiring access to source code, seamlessly integrating into existing build processes via NuGet or MSBuild.
Strong-name sign third party .NET assemblies without the source code.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Signs third-party .NET assemblies without needing the original source, directly addressing the 'Referenced assembly does not have a strong name' compilation error mentioned in the README.
Automatically rewrites assembly references, InternalsVisibleTo attributes, and BAML resources for WPF (as of version 3.x), ensuring dependency integrity after signing.
Integrates into Visual Studio builds via MSBuild targets or as a NuGet package, automating signing in CI/CD pipelines, with examples provided for pre-build steps.
Processes multiple interdependent assemblies in a single command using wildcards or piped directories, as shown in the Elmah and ServiceStack examples, to handle complex dependency chains.
Requires all interdependent assemblies to be processed together in one call, leading to verbose and error-prone MSBuild scripts, as illustrated with ServiceStack dependencies.
Alters third-party assembly binaries, which can introduce compatibility issues, break functionality, or violate licenses without built-in safeguards.
README emphasizes .NET Framework and WPF BAML updates, with no explicit support for newer .NET versions like .NET 5+ or Blazor, potentially reducing relevance for modern projects.
Integration requires manual editing of project files or NuGet package management, adding complexity compared to native signing methods available in source-controlled projects.