[Mono-bugs] [Bug 54044][Min] Changed - mcs-0.30 compiled exe cannot run under Microsoft .net 1.1

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Sun, 8 Feb 2004 14:58:23 -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 atsushi@ximian.com.


--- shadow/54044	2004-02-08 13:07:12.000000000 -0500
+++ shadow/54044.tmp.15723	2004-02-08 14:58:23.000000000 -0500
@@ -1,15 +1,15 @@
 Bug#: 54044
 Product: Mono/Compilers
 Version: unspecified
 OS: unknown
 OS Details: 
-Status: NEW   
+Status: RESOLVED   
+Resolution: NOTABUG
 Severity: Unknown
-Priority: Major
+Priority: Minor
 Component: C#
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: liyul@hotmail.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -42,6 +42,24 @@
 ------- Additional Comments From liyul@hotmail.com  2004-02-08 13:07 -------
 BTW, it is Windows XP home edition for this bug. Didn't test other OS.
+------- Additional Comments From atsushi@ximian.com  2004-02-08 14:58 -------
+What is "Shawna Van Ness's timesetter.cs" ? Is it any special kind of 
+programs? Anyways...
+> Should have it set to much Microsoft .net 1.0/1.1
+> public key token when applicable
+Public key is used to prove the origin of the assembly. It is 
+possible only when we have the same private key as Microsoft people 
+internally use.
+This is Microsoft's problem that if their runtime does not allow our 
+class libraries when our dlls are correctly put in their probed PATH 
+(if their CLR runtime is really "binary compatible, it should be).
+Note that ms signed System.dll and our System.dll are different 
+assemblies. If they are regarded as the same, it will cause so called 
+DLL hell.