[Mono-bugs] [Bug 21420] Changed - custom attributes defined in the same assembly problem

bugzilla-daemon@rocky.ximian.com bugzilla-daemon@rocky.ximian.com
12 Apr 2002 16:56:09 -0000

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 ravi@ximian.com.


--- shadow/21420	Fri Apr 12 09:15:19 2002
+++ shadow/21420.tmp.1815	Fri Apr 12 12:56:09 2002
@@ -53,6 +53,27 @@
 strategy because if it requires support in reflection, I'd like to
 start writing it before you commit your code to cvs or we'll have a
 non-working build for some time and that's bad... Or are you writing
 the reflection support code as well? If you continue using the
 SetCustomAttribute (CustomAttributeBuilder cb) interface, you _need_
 to write support in reflection for it. Please tell us what you're doing.
+------- Additional Comments From ravi@ximian.com  2002-04-12 12:56 -------
+Hi Lupus!
+  The thing is that the current code fails because the attribute type
+is not registered correctly and this has to do with the order in which
+types are populated. This is turning out to be very complicated and my
+strategy is first to tackle the problem that currently exists with the
+global attributes grammar. 
+  I do not intend using anything but SetCustomAttribute
+(CustomAttributeBuilder cb) for now so it would be good if those
+reflection bits are filled in. Of course, I may be completely wrong
+about this and perhaps we will then have to do it your way ;-) 
+  You may go ahead and fill in the reflection bits for the existing
+code. I need more time to start working on this because your sample
+runs into a number of issues, the first of which I am tackling right now.