[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-16 21:44:59.000000000 -0400
+++ shadow/62829.tmp.6543	2004-09-17 16:57:33.000000000 -0400
@@ -1,17 +1,17 @@
 Bug#: 62829
 Product: Mono: Class Libraries
 Version: unspecified
 OS: unknown
 OS Details: 
-Status: REOPENED   
+Status: NEW   
 Resolution: 
 Severity: Unknown
 Priority: Normal
 Component: CORLIB
-AssignedTo: mono-bugs@ximian.com                            
+AssignedTo: sebastien@ximian.com                            
 ReportedBy: marek.safar@seznam.cz               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
 Summary: TypeBuilder.AddDeclarativeSecurity
@@ -100,6 +100,15 @@
 constant) encoding problem (as MS PEVerify doesn't flag any error on
 the compiled assembly).
 
 ------- Additional Comments From sebastien@ximian.com  2004-09-16 21:44 -------
 Oops forget to say that the assembly-level attributes have the same
 problem.
+
+------- Additional Comments From sebastien@ximian.com  2004-09-17 16:57 -------
+The problem is more random than I thought. 
+
+* All kind of permissions always work with Mono.
+
+* On MS runtime they seems to work only in certain conditions - so it
+is possible to have (or not) security attributes on
+assembly/type/method but mixing them gets mixed results.