[Mono-bugs] [Bug 75246][Nor] Changed - KeyPair of AssemblyName used to create assembly has no effect on AssemblyName of AssemblyBuilder

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon Jun 13 15:06:22 EDT 2005

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 at ximian.com.


--- shadow/75246	2005-06-13 13:49:24.000000000 -0400
+++ shadow/75246.tmp.23296	2005-06-13 15:06:22.000000000 -0400
@@ -55,6 +55,27 @@
 with Category "NotWorking" for now).
 ------- Additional Comments From gert.driesen at pandora.be  2005-06-13 02:41 -------
 Created an attachment (id=15313)
 source code for repro
+------- Additional Comments From sebastien at ximian.com  2005-06-13 15:06 -------
+Hello Gert, 
+you may want to try the attached patch (which will get into SVN after
+the 1.1.8 release). The "main" problem (KeyPair) is fixed but...
+(a) I had to choose between returning null (your test case) and
+returning "new byte [0]" (current behavior) for GetPublicKey. There's
+a unit test that shows (under both 1.x and 2.0) the 0-length array.
+I've tagged this case as "NotWorking" as your's (null) simpler. Maybe
+someday someone will find out when/why [0] is returned...
+(b) the AssemblyName still returns an extra "culture=neutral". There
+is already a bug about that.
+(c) unit tests #8 and #16 (abName.CultureInfo !=
+CultureInfo.InvariantCulture) aren't related to #75246 nor to public
+keys. Same for some NET_2_0 tests. So I copied the
+AssemblyName_PublicKey test to a new AssemblyName_MoreCultureInfo to
+split the tests.

More information about the mono-bugs mailing list