[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 16:56:21 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 16:02:03.000000000 -0400
+++ shadow/75246.tmp.25621	2005-06-13 16:56:21.000000000 -0400
@@ -112,6 +112,25 @@
 managed code, but I'm not enough familiar with the runtime (and I'm 
 afraid most of the work must be done there).
 Note: I have not verified this yet !! But I'm pretty sure lots (?) 
 of our AssemblyName tests (if they're not disabled)fail on MS.NET 
 1.x (and definitely on 2.0)
+------- Additional Comments From sebastien at ximian.com  2005-06-13 16:56 -------
+Gert, the manual vs created AssemblyName may be difference (it's worth
+investigating). As for the other comments:
+* the null versus [0] array happens on both 1.x and 2.0 runtime (see
+AssemblyNameTest.Self test case). There may be other differences/cases
+but I'm not aware of them.
+* (with one recent exception) all the AssemblyName tests runs
+successfully on both Mono 1.1.x and MS 1.x (I just tested then again
+to be 100% sure). All tests _were_ working with 2.0 prior to beta2 but
+it seems no one has yet taken the time to update the test suite since
+beta2 was released. I'll update AssemblyNameTest ASAP.
+* most of this can be (and should be) dealt in managed code (e.g. it
+much easier to have 1.x/2.0 behavior differences there).
+Your help is always appreciated. Thanks :-)

More information about the mono-bugs mailing list