RE: [xsl] calling two consecutive xsl files

Subject: RE: [xsl] calling two consecutive xsl files
From: Pieter Reint Siegers Kort <pieter.siegers@xxxxxxxxxxx>
Date: Thu, 10 Mar 2005 16:18:12 -0600

ASP.NET and ASP can coexist on one web server. And it's not that platform
specific as you think it is (yes, classic ASP was, but that goes for many
script languages, even today) - since the .NET Framework is built on an ECMA
standard (the CLI - see
you'll easily find your way to Linux and Mac OSX through Mono compatible
projects. Develop in Windows and deploy almost anywhere, I'd say.

To stay on the XSLT 2.0 track, MS will not add any XSLT 2.0 until there is a
stable W3C Rec available - at least that is what I've picked up until now -
so that's why we've started the Saxon.NET effort. Although early and a bit
slow I'd say it is a wonderful step forward.


-----Original Message-----
From: Antsnio Mota [mailto:amsmota@xxxxxxxxx]
Sent: Jueves, 10 de Marzo de 2005 02:48 p.m.
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] calling two consecutive xsl files

Hmmm, since i'm not a english native *and* not a MS expert, the "terrific"
here is a good thing or a bad thing? It's "terrific" in the sense of
"terror" or in the sense of "uau!".

Or simply putting it it's   :)    or    :(   ?

Now we're using a IIS with asp on it, but i'll prefer a platform agnostic
thing. The upgrade(?) a "normal" asp to is straithforward?

On Thu, 10 Mar 2005 13:36:04 -0600, Pieter Reint Siegers Kort
<pieter.siegers@xxxxxxxxxxx> wrote:
> One way would be to upgrade to ASP.NET with its terrific XML support,
> and use Saxon.NET which supports XSLT 2.0.
> NB1: Saxon.NET is an OS effort to port the great Saxon product to .NET
> and Mono. All functionality offered has its origin in Saxon, therefore
> all credits go to its creator, Michael Kay.
> NB2: Saxon.NET is still an early beta product, and is currently about
> 25% slower than using Saxon (on Windows). There is a workaround to
> this - you can spawn processes in ASP.NET which run Saxon
> transformations in the background and return to you the output, which
> is the same as running Saxon from the command line, and thus has the same
> Cheers,
> <prs/>

Current Thread