Skip to content

Releases: brutaldev/StrongNameSigner

2.1.0

24 Sep 19:53
Compare
Choose a tag to compare

Fixes a major problem in signing caused by trying to cache assemblies. New dependencies always need to be read before trying a new round of fixes. Caching still applies when getting the assembly info to inspect so detecting whether an assembly is signed is very fast.

If you are using v2.0, please update to v2.1 as soon as possible to ensure files are signed and fixed reliably.

1.8.0

05 May 19:06
Compare
Choose a tag to compare

Fix major problem with source files getting overwritten if friend assemblies are fixed. This will happen if you specify an output directory, the source files are actually updated not the new signed files in the output location.
Enable reading and writing of PDB files if they are found (Issue #11).

1.7.0

14 Apr 14:50
Compare
Choose a tag to compare

Allow for wildcards in the input directory list (issue #19 and #20).

1.6.1

07 Jan 10:56
Compare
Choose a tag to compare

Use all specified assembly probing paths to find references when signing. Works better with NuGet packages.

1.5.1

08 Aug 13:25
Compare
Choose a tag to compare

Ensure any assembly write gets re-signed as well. This is safe with the generated key being cached now and avoid friend assembly and reference fixes from breaking the validity. Fixes ordering problem with assembly signing in issue #16.

1.5.0

04 Jul 23:48
Compare
Choose a tag to compare

Fix strange issue #16 where the same generated strong name would not be valid every time. Caching the byte array instead of the StrongNameKeyPair class and recreating it every time works well on the target project.

1.4.9

01 Jul 18:41
Compare
Choose a tag to compare

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

This release is backward compatible with previous releases.

Fixes issue #16.

1.4.8

30 May 18:41
Compare
Choose a tag to compare
  • Auto correction of referenced versions. Unsigned assembly versions don't matter in the reference so it's safe to take a signed version and use it's reference. There are a few NuGet packages that reference versions that other assemblies don't and there is not way to use them with normalizing the version.
  • Provide all included assembly paths as probing paths for references. This makes reference fixing much easier since no assemblies need to be copied to the signed assembly location. Referenced assemblies are determined from the list of included assemblies (already signed or not).

1.4.7

28 May 21:02
Compare
Choose a tag to compare

Updated Cecil and PowerArgs versions.
Better help output.
Fix color output always being green (even for errors)...

1.4.6

28 May 11:12
Compare
Choose a tag to compare

Added an optional LogLevel (or -l for short) parameter to the console app to control the output in response to request #15.

Usage Example: -l Silent

Level Description
Default This is the same as Verbose.
Verbose Log everything as it did before including banner.
Changes Log only when changes are made to files and include the final summary.
Summary Only show the final summary of the signing operation.
Silent Output nothing (except of course errors and warnings).

NB: Errors and warnings are always output to the console even when Silent is used.