Releases: brutaldev/StrongNameSigner
3.6.3
What's Changed
- Fix issue #108 by adding the NuGet package path as a probe location for dependency resolution as well as adding other app and ref paths for Microsoft libraries.
This increases the time taken to sign assemblies because of potentially massive NuGet package directories but in terms of reliability there should never be another dependency resolution error unless you don't actually install the package (which would install int's dependencies as well).
NuGet: https://www.nuget.org/packages/Brutal.Dev.StrongNameSigner/3.6.3
Full Changelog: v3.6.2...v3.6.3
3.6.2
What's Changed
- Fix issue #107 by handling custom attribute fixing for multiple versions of the same assembly with the same name.
NuGet: https://www.nuget.org/packages/Brutal.Dev.StrongNameSigner/3.6.2
Full Changelog: v3.6.1...v3.6.2
3.6.1
3.5.1
Fix #101 - Disable FIPS enforcement in configuration.
NuGet: https://www.nuget.org/packages/Brutal.Dev.StrongNameSigner/3.5.1
Full Changelog: v3.5.0...v3.5.1
3.5.0
3.4.0
3.3.3
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.
NuGet: https://www.nuget.org/packages/Brutal.Dev.StrongNameSigner/3.3.3
3.3.2
- Update custom attributes with type reference arguments.
- Remove unreferenced friend assemblies.
NuGet: https://www.nuget.org/packages/Brutal.Dev.StrongNameSigner/3.3.2
3.3.1
- Fix task order default values.
NuGet: https://www.nuget.org/packages/Brutal.Dev.StrongNameSigner/3.3.1
3.3.0
- 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.
NuGet: https://www.nuget.org/packages/Brutal.Dev.StrongNameSigner/3.3.0