[Mono-bugs] [Bug 53292][Min] Changed - SetCustomAttribute opens key file for AssemblyKeyFileAttribute

[bugzilla-daemon@bugzilla.ximian.com]

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 spouliot@videotron.ca.

http://bugzilla.ximian.com/show_bug.cgi?id=53292

--- shadow/53292	2004-01-24 07:36:51.000000000 -0500
+++ shadow/53292.tmp.7275	2004-01-26 13:32:38.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 53292
 Product: Mono/Class Libraries
 Version: unspecified
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Minor
 Component: CORLIB
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: dave-mono@earth.li               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -27,6 +27,22 @@
 On an AssemblyBuilder, it throws an IOException if it cannot find a file
 named "foo".  This seems sensible, however it doesn't seem to happen on
 MS.NET. 
 
 This is in the test cases in: 
 MonoTests.System.Reflection.Emit.AssemblyBuilderTest.TestSetCustomAttribute
+
+------- Additional Comments From spouliot@videotron.ca  2004-01-26 13:32 -------
+The TestSetCustomAttribute method generates the assembly
+TestSetCustomAttribute.dll (normally deleted after the test). ILDASM
+shows that the AssemblyKeyFileAttribute is indeed present in the assembly.
+
+  .custom instance void
+[mscorlib]System.Reflection.AssemblyKeyFileAttribute::.ctor(string) =
+( 01 00 03 66 6F 6F 00 00 )                         // ...foo..
+
+However the assembly ISN'T strongnamed (tested with both MS sn and
+secutil tools).
+
+We are (probably) not strongnaming the assembly at the right place
+(SetCustomAttribute). Maybe some works is done directly in csc ? if
+only to show the right error message (CS1548) when the file is missing ?