[Mono-bugs] [Bug 55919][Nor] Changed - [PATCH] Assembly version for references to system assemblies hard coded to 1.0.3300.0
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Sat, 27 Mar 2004 15:49:06 -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=55919
--- shadow/55919 2004-03-26 10:05:14.000000000 -0500
+++ shadow/55919.tmp.9409 2004-03-27 15:49:06.000000000 -0500
@@ -11,13 +11,13 @@
AssignedTo: sebastien@ximian.com
ReportedBy: gert.driesen@pandora.be
QAContact: mono-bugs@ximian.com
TargetMilestone: ---
URL:
Cc:
-Summary: Assembly version for references to system assemblies hard coded to 1.0.3300.0
+Summary: [PATCH] Assembly version for references to system assemblies hard coded to 1.0.3300.0
BugsThisDependsOn: 55563
In resolution_scope_from_image (reflection.c), the major version and build
number is hard coded to 1 and 3300 for references to system assemblies.
The build version should ofcourse be 5000 for compatibility with .NET 1.1.
@@ -43,6 +43,14 @@
The problem seems that mono_metadata_decode_row_col returns NULL in
mono_metadata_decode_row_col. It may be related to the fact that
monosn can't extract the public key from the assembly while sn.exe
(both Mono's managed and MS implementation) can.
+
+------- Additional Comments From sebastien@ximian.com 2004-03-27 15:49 -------
+This patch use the mono_metadata_decode_row function (instead of
+mono_metadata_decode_row_col) to fix mono_image_get_public_key.
+
+This does fix the current problem, which is to take the information
+from the referenced assemblies (when assemblies are strongnamed), but
+doesn't fix the mono_metadata_decode_row_col (nor the monosn failures).