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.
1bb378f6-9b72-47b0-9c07-5b6758237326|1|1.0