Softpedia >Windows >Security >Security Related >Brutal Developer .NET Assembly Strong-Name Signer >  Changelog

Brutal Developer .NET Assembly Strong-Name Signer Changelog

What's new in Brutal Developer .NET Assembly Strong-Name Signer 3.5.0.0

Feb 5, 2024
  • Fixed:
  • Add additional probing paths for legacy .NET framework assembly signing.

New in Brutal Developer .NET Assembly Strong-Name Signer 3.3.3.0 (Jan 21, 2023)

  • 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.

New in Brutal Developer .NET Assembly Strong-Name Signer 3.3.2.0 (Jan 12, 2023)

  • Update custom attributes with type reference arguments.
  • Remove unreferenced friend assemblies.

New in Brutal Developer .NET Assembly Strong-Name Signer 3.3.1.0 (Jan 10, 2023)

  • Fix task order default values.

New in Brutal Developer .NET Assembly Strong-Name Signer 3.3.0.0 (Jan 5, 2023)

  • Added ability to control when SNS is executed.
  • Fix probing issues on full .NET assembly loading.
  • Fixed file locking issues preventing signing (can still have errors deleting new temporary files).
  • Added extra logging.

New in Brutal Developer .NET Assembly Strong-Name Signer 3.2.1.0 (Dec 19, 2022)

  • Prevent locking issues with friend references being written after their referencing assemblies.
  • No longer remove friend references for assemblies not included in the signing list.
  • Minor optimizations.

New in Brutal Developer .NET Assembly Strong-Name Signer 3.2.0.0 (Dec 16, 2022)

  • Optional OutputPath and recover from locked file copy failures..
  • Provide KeyFile and Password parameters.
  • Add condition to disable automatic signing.

New in Brutal Developer .NET Assembly Strong-Name Signer 3.1.1.0 (Jan 11, 2022)

  • Fix DPI scaling issues (#68)
  • No changes to the build tasks, NuGet package or console application, just the user interface,

New in Brutal Developer .NET Assembly Strong-Name Signer 3.1.0.0 (Dec 31, 2021)

  • Fix issue #31, BAML rewriting has been added.
  • Fix issue #42, mixed-mode assembly signing working.
  • Fix issue #52, cross-platform signing working.
  • Fix issue #62, automated build task ignores cached NuGet package locations.

New in Brutal Developer .NET Assembly Strong-Name Signer 2.9.1.0 (Nov 17, 2021)

  • Fix issues #66.
  • Remove validation for missing key file (will generate one).

New in Brutal Developer .NET Assembly Strong-Name Signer 2.9.0.0 (Nov 2, 2021)

  • Fix issues #38 and tested #44.
  • Update version numbers.
  • Ignore delay signed assemblies that simply throw exception.
  • Fix password field not being disabled in the UI.
  • Update packages.

New in Brutal Developer .NET Assembly Strong-Name Signer 2.7.1 (Dec 12, 2019)

  • 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.

New in Brutal Developer .NET Assembly Strong-Name Signer 2.7.0 (Dec 12, 2019)

  • 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.

New in Brutal Developer .NET Assembly Strong-Name Signer 2.6.0 (Nov 25, 2019)

  • Add ability to disable console signing using an environment variable called SNS_DISABLE_CONSOLE_SIGNING. Valid values are true or false (Issue #56).
  • Added ability to detect delay-signed assemblies and treat them as being unsigned (Issue #53).

New in Brutal Developer .NET Assembly Strong-Name Signer 2.4.0 (Sep 19, 2019)

  • Create temp folder away from the source of the files being signed.
  • Updated to latest Mono.Cecil (0.11), possibly fixes a number of .NET Core signing issues.

New in Brutal Developer .NET Assembly Strong-Name Signer 2.3.0 (Aug 29, 2018)

  • Better handling of PDB files

New in Brutal Developer .NET Assembly Strong-Name Signer 2.2.0 (Aug 29, 2018)

  • Update to the latest version of Mono.Cecil.
  • Fix file locking issues that appeared as a result of the update.
  • Cache differently to avoid file locks (issue #47).

New in Brutal Developer .NET Assembly Strong-Name Signer 2.1.4 (Jan 19, 2018)

  • Reset the read-only file attribute on any files before they are copied or signed

New in Brutal Developer .NET Assembly Strong-Name Signer 2.1.3 (May 15, 2017)

  • Includes the ability to set the $(StrongNameSignerDirectory) variable (issue #37).
  • No code changes.

New in Brutal Developer .NET Assembly Strong-Name Signer 2.1.2 (May 15, 2017)

  • Do not use cache if file contents have changed (issue #34).
  • Revert back to stable Mono.Cecil because the new version (beta5) locks files on disk (issue #35)

New in Brutal Developer .NET Assembly Strong-Name Signer 2.1.1 (May 2, 2017)

  • Do not use cache if file contents have changed (issue #34).
  • Revert back to stable Mono.Cecil because the new version (beta5) locks files on disk (issue #35)

New in Brutal Developer .NET Assembly Strong-Name Signer 2.0.0 (Sep 19, 2016)

  • Add build task to perform automatic signing when NuGet package is installed.
  • Major performance improvement with caching assembly definitions and avoiding tons of I/O.
  • If you are upgrading from v1.x and you are using the custom build execution task, you will need to change the path to the console application from tools to build.
  • A build task will also automatically be added to your project file which you may want to remove if you're happy with your custom configuration.

New in Brutal Developer .NET Assembly Strong-Name Signer 1.8.0 (Jul 8, 2016)

  • 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).

New in Brutal Developer .NET Assembly Strong-Name Signer 1.7.0 (Jul 8, 2016)

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

New in Brutal Developer .NET Assembly Strong-Name Signer 1.6.1 (Jul 8, 2016)

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

New in Brutal Developer .NET Assembly Strong-Name Signer 1.5.1 (Jul 8, 2016)

  • 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.

New in Brutal Developer .NET Assembly Strong-Name Signer 1.5.0 (Jul 8, 2016)

  • 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.

New in Brutal Developer .NET Assembly Strong-Name Signer 1.4.9 (Jul 8, 2016)

  • 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.

New in Brutal Developer .NET Assembly Strong-Name Signer 1.4.8 (Jul 8, 2016)

  • 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).

New in Brutal Developer .NET Assembly Strong-Name Signer 1.4.7 (Jul 8, 2016)

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

New in Brutal Developer .NET Assembly Strong-Name Signer 1.4.6 (Jul 8, 2016)

  • 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