<xsl:message> which does nothing in IE unless the terminate is set to yes, making it useless for debug tracing. Their latest MSDN documentation indicates the messages are stored in a buffer somewhere, but it's doubtful their intrepid web traveler gives us anyway to access it -- I couldn't find anything on it myself. Here Mozilla's conflagration canine shines with all the strings printed in the Error Log.As for processing XSL documents with MSXML ...
If terminate is set to "no", then the Microsoft XML Parser (MSXML) 3.0 ignores the command. This is a good way to disable error handling without removing it entirely from your Extensible Stylesheet Language (XSL) style sheet, although upcoming implementations can send such messages out to a log file. (This is not currently supported.)Sadly the Object Viewer reveals I'm using some version 6 interface and still don't see any properties/functions for capturing messages during XSL transformations.
Kinda funny: in looking for the main MSXML website, I tried http://www.microsoft.com/xml and it responds successfully (HTTP 200) with an utterly element free "HTML" document stating: "The page cannot be displayed because an internal server error has occurred." Hmm, I wonder if this bodes well for using their object.
0 comments:
Post a Comment