[Mono-bugs] [Bug 62372][Wis] Changed - GetCustomAttributes does not return pseudo-attributes (2.0)

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Wed, 11 Aug 2004 19:31:23 -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/62372	2004-08-11 18:41:54.000000000 -0400
+++ shadow/62372.tmp.28342	2004-08-11 19:31:23.000000000 -0400
@@ -11,13 +11,13 @@
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: duncan@ximian.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
-Summary: GetCustomAttributes does not return SerializableAttribute (2.0)
+Summary: GetCustomAttributes does not return pseudo-attributes (2.0)
 Given something like:
 using System;
 class FooAttribute : Attribute {}
@@ -66,6 +66,21 @@
 So far I've seen that System.NonSerializedAttribute is also reported
 (still in error in corcompare). SecurityAttribute-derived attributes
 are not reported by GetCustomAttributes (and shows up as extra right
 now due to bad encoding, see 62358 for more details).
 I'll log what I find into this bug report.
+------- Additional Comments From sebastien@ximian.com  2004-08-11 19:31 -------
+Field.IsNotSerialized is probably responsible for the
+[NonSerializable] attribute.
+Also found out (AppDomain.GetCurrentThreadId) that
+* System.Runtime.InteropServices.DllImportAttribute
+* System.Runtime.InteropServices.PreserveSigAttribute
+are also added as attributes. 
+I think my previous (managed) patch isn't appropriate as some
+attributes have fields/properties unknown in managed code. Maybe it
+would be better to change the icall to add a boolean "pseudoAttribute"
+(true for 2.0 and false for 1.0/1.1). :-(