[Mono-bugs] [Bug 56564][Nor] Changed - Incorrect description for CS1548 when the strongname file doesn't contain the private key

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Wed, 7 Apr 2004 07:44:27 -0400 (EDT)

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.


--- shadow/56564	2004-04-07 02:34:21.000000000 -0400
+++ shadow/56564.tmp.26153	2004-04-07 07:44:27.000000000 -0400
@@ -1,12 +1,12 @@
 Bug#: 56564
 Product: Mono: Compilers
 Version: unspecified
 OS: unknown
 OS Details: 
-Status: NEW   
+Status: ASSIGNED   
 Severity: Unknown
 Priority: Normal
 Component: C#
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: sebastien@ximian.com               
@@ -57,6 +57,23 @@
 ------- Additional Comments From miguel@ximian.com  2004-04-07 02:34 -------
 Sebastien, can you please apply this patch, it looks good to me.
 Question: will the compiler continue to work on MS.NET?
+------- Additional Comments From sebastien@ximian.com  2004-04-07 07:44 -------
+Yes :)
+A COMException is throw on MS runtime _only_ when you try to embed the
+ECMA key within the assembly. I'll rework the patch so we report the
+CS1606 error like CSC in this case.
+The end result will be:
+a. On MS runtime MCS will report CS1606 like CSC when the ECMA key is
+specified with AssemblyKeyFile.
+b. On Mono runtime MCS will successfully compile the assembly.
+We may have to use the _monocs_ (or something like this) around the
+AssemblyKeyFile for the ECMA signed assemblies so they still compile
+on Windows. But we wont be able to put ECMA assemblies compiled with
+CSC in the GAC.