[Mono-bugs] [Bug 70841][Nor] Changed - mono-ecma.xsl transformation results in XsltException under MS.NET

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

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

--- shadow/70841	2004-12-30 15:00:21.000000000 -0500
+++ shadow/70841.tmp.4871	2004-12-30 15:17:01.000000000 -0500
@@ -10,13 +10,13 @@
 Component: Sys.XML
 AssignedTo: atsushi@ximian.com                            
 ReportedBy: atsushi@ximian.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
 URL: 
-Summary: mono-ecma.xsl transformation results in XsltException under MS.NET (CAS matter)
+Summary: mono-ecma.xsl transformation results in XsltException under MS.NET
 
 running monodoc's EcmaHelpSource.Htmlize() under MS.NET results in an
 exception with related to handling extension object, while Mono does not
 (not sure if it is mono bug right now).
 
 Actual Results:
@@ -98,6 +98,15 @@
 
 e.g.
 args.AddExtensionObject("monodoc://extensions", ExtObject);
 
 and the exception is thrown later because something (the monodoc
 object) is missing.
+
+------- Additional Comments From atsushi@ximian.com  2004-12-30 15:17 -------
+ah ;-)
+
+Well, monodoc:// is just a namespace URI for XML. There is nothing
+being resolved with related to that URI scheme. MS's default
+XmlResolver used in XslTransform might be XmlSecureResolver and that
+would block nonpublic method execution. Note that the stack trace
+shows that it already got MethodInfo (RuntimeMethodInfo) to execute.