[GH-ISSUE #15] Add a verbosity switch #15

Closed
opened 2026-02-25 21:30:28 +03:00 by kerem · 2 comments
Owner

Originally created by @mklaber on GitHub (May 27, 2015).
Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/15

Originally assigned to: @brutaldev on GitHub.

Now that I've actually added this to my build process I'm faced with the incredibly verbose output it produces. While a "silent" mode would be nice, I probably wouldn't want it that quiet. It'd be great if it'd just print the assemblies that are fixed or signed. (e.g., don't print assemblies that have a Nothing to fix... result)

Originally created by @mklaber on GitHub (May 27, 2015). Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/15 Originally assigned to: @brutaldev on GitHub. Now that I've actually added this to my build process I'm faced with the incredibly verbose output it produces. While a "silent" mode would be nice, I probably wouldn't want it that quiet. It'd be great if it'd just print the assemblies that are fixed or signed. (e.g., don't print assemblies that have a `Nothing to fix...` result)
kerem 2026-02-25 21:30:28 +03:00
Author
Owner

@brutaldev commented on GitHub (May 28, 2015):

LogLevel parameter provided in v1.4.6.

In your case, you would want to use the Changes level to only output any changes made (includes signing, reference corrections and IVT removals). Simply add -l Changes to your command-line arguments.

Certain log messages have been changed to ensure you are always aware of the file name being operated on.

<!-- gh-comment-id:106281026 --> @brutaldev commented on GitHub (May 28, 2015): `LogLevel` parameter provided in [v1.4.6](https://github.com/brutaldev/StrongNameSigner/releases/tag/v1.4.6). In your case, you would want to use the `Changes` level to only output any changes made (includes signing, reference corrections and IVT removals). Simply add `-l Changes` to your command-line arguments. Certain log messages have been changed to ensure you are always aware of the file name being operated on.
Author
Owner

@mklaber commented on GitHub (May 28, 2015):

Awesome, as always.

<!-- gh-comment-id:106333096 --> @mklaber commented on GitHub (May 28, 2015): Awesome, as always.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/StrongNameSigner#15
No description provided.