Re: Upgrading from server side MSXML to Saxon.Net

On Thu, May 22, 2008 at 2:52 AM, Andrew Welch <andrew.j.welch@xxxxxxxxx> wrote:
> How straightforward is to upgrade from MSXML 4 to Saxon.Net in ASP.Net?

Easy, if the apps do not use extension functions. May be challenging
if such are used all over the place. Upgrading from MSXML even to the
.NET XSLT processors XslTransform and XslCompiledTransform can be
challenging -- VBScript is no longer supported for writing inline
extension functions, JScript is different in the two environments,
etc. ...

Besides this, all known issues of processing an XSLT 1.0
transformation with an XSLT 2.0 processor (even in backwards
compatibility mode).

I do not have an example of successfully running Saxon.NET within IE
-- transformations designed to be run within or by IE may be
challenging to convert to using Saxon.NET.





-- 
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
---------------------------------------
To invent, you need a good imagination and a pile of junk
-------------------------------------
Never fight an inanimate object
-------------------------------------
You've achieved success in your field when you don't know whether what
you're doing is work or play