[Mono-bugs] [Bug 62829][Nor] Changed - TypeBuilder.AddDeclarativeSecurity

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

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

--- shadow/62829	2004-09-17 17:41:42.000000000 -0400
+++ shadow/62829.tmp.5602	2004-09-20 09:45:20.000000000 -0400
@@ -117,6 +117,18 @@
 Hmmm... from a few more tests it looks like the ordering could be
 important. Which would means assembly security attributes should be
 first (which normally would be the case using AssemblyBuilder) except
 that MCS has a "hack" to do this later (design issue). 
 
 Anyway more tests another day.
+
+------- Additional Comments From sebastien@ximian.com  2004-09-20 09:45 -------
+100% sure: CSC (well MS S.R.E) always encode the token with acsending
+numbers.
+100% sure: MCS (well Mono S.R.E.) encode the token in the order they
+are added (e.g. assemblies always get last with token 1).
+98% sure: All results I have indicates that MS runtime stop looking
+decl attributes when the next token < current token.
+
+Partition II, section 21.11 doesn't list ordering as important
+(warning or error) but maybe this is discuted elsewhere in a more
+general section ?