[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Drop-in replacement for MSXML to get to XSL2.0
On 31/05/2012 00:26, Mark Anderson wrote:
Hi GuysThe difference between VB6 and VB.net here is rather important. I think the closest thing to an XSLT 2.0 processor that runs as a COM component is the Altova processor. They chose not to emulate the MSXML API very closely; in particular, as far as I can see, they only work with "lexical XML" as input and output, not with MSXML DOM documents. They no doubt had good reasons for this decision: because MSXML has such close coupling between parsing, validation, and transformation, it can make it difficult to just replace the transformation part with a different engine. For .NET the story is rather different, since there are's a choice of several XSLT 2.0 processors for .NET, including Saxon. The APIs for Saxon are not a direct emulation of either MSXML or the native .NET transformation engine (one reason being that the APIs are defined as concrete classes rather than interfaces, as Microsoft clearly never envisaged an alternative implementation being provided.) However, in designing the .NET interface for Saxon we did try to integrate as much as possible with the XML classes in the .NET framework. Michael Kay Saxonica
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|