[Mono-bugs] [Bug 80225][Nor] New - AssemblyName.GetPublicKey() should not return null
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Mon Dec 11 13:24:10 EST 2006
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 knocte at gmail.com.
http://bugzilla.ximian.com/show_bug.cgi?id=80225
--- shadow/80225 2006-12-11 13:24:10.000000000 -0500
+++ shadow/80225.tmp.12568 2006-12-11 13:24:10.000000000 -0500
@@ -0,0 +1,35 @@
+Bug#: 80225
+Product: Mono: Class Libraries
+Version: 1.2
+OS: All
+OS Details:
+Status: NEW
+Resolution:
+Severity: Unknown
+Priority: Normal
+Component: CORLIB
+AssignedTo: mono-bugs at ximian.com
+ReportedBy: knocte at gmail.com
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL:
+Cc:
+Summary: AssemblyName.GetPublicKey() should not return null
+
+The new beta version of the (OSS) NHibernate project (which now supports
+2.0 stuff like Generics and Nullables) relies on the behaviour of the
+GetPublicKey() method of AssemblyName class about not returning null, but a
+vector of 0 bytes (so as to be able to query the Length property); so it
+generates an NRE when using it with Mono.
+
+In fact, there is a FIXME related to this bug in
+mcs/class/corlib/System.Reflection/AssemblyName.cs:
+
+public byte[] GetPublicKey()
+{
+ return publicKey;
+ // FIXME: In some cases MS implementation returns
+ // "new byte [0]" instead of null
+}
+
+I'm going to propose a small patch.
More information about the mono-bugs
mailing list