[Mono-bugs] [Bug 71190][Wis] Changed - Cecil shows null for the specified assembly public key token

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Wed, 12 Jan 2005 11:17:36 -0500 (EST)


Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by sebastien@ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=71190

--- shadow/71190	2005-01-11 22:08:55.000000000 -0500
+++ shadow/71190.tmp.11610	2005-01-12 11:17:36.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 71190
 Product: Mono: Class Libraries
 Version: 1.1
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Wishlist
 Component: Mono.Cecil
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: sebastien@ximian.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -37,6 +37,18 @@
 Additional Information:
 * This can also be seen in the screenshot
 http://evain.net/public/cecil_feed_alpha.png
 
 * The public key token is/may not be available and must be calculated from
 the complete public key.
+
+------- Additional Comments From sebastien@ximian.com  2005-01-12 11:17 -------
+There is one problem to compute the "correct"(*) public key token from
+the public key is that the hash algorithm is part of the
+AssemblyDefinition class (and not part of the AssemblyName). Otherwise
+Cecil could always use SHA-1 to generate the public key token.
+
+I think it would make more sense to have the hash algorithm inside the
+AssemblyName (like it is in the System.Reflection.AssemblyName).
+
+(*) I say "correct" because I've never seen MD5 used to compute a
+public key token - but it's still in the spec so...