Releases: brutaldev/StrongNameSigner
2.1.0
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
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
1.6.1
1.5.1
1.5.0
1.4.9
1.4.8
- 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
1.4.6
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.