So this is more of an annoyance than a bug, but you should be aware of the following:
If using SN.EXE to extract your public key information, and you supply an invalid file name or path, SN.EXE just states that your assembly “does not represent a strongly named assembly.”
If you run the same command on a assembly that does exist, but isn’t signed…guess what, you get the same error message. Misleading, very misleading.
Be the first to rate this post
- Currently 0/5 Stars.
- 1
- 2
- 3
- 4
- 5