OK, all processing is going to be done on our server. Does Saxon have a
.NET wrapper? If not, is there another XSLT processor that will work
with both XSLT2 and .NET?
-----Original Message-----
From: owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
[mailto:owner-xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com] On Behalf Of
Kienle,
Steven C [USCRE/0924]
Sent: Wednesday, November 19, 2003 12:16 PM
To: 'xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com'
Subject: RE: [xsl] XSL Tool
If your users will be processing the XSLT on their computers and you
have no
control over those workstations, you should not expect anything more
than
XSLT 1.0. Also, you should test the code on as many possible XSLT
processors as you can.
Steve
-----Original Message-----
From: kakridge(_at_)bellsouth(_dot_)net
[mailto:kakridge(_at_)bellsouth(_dot_)net]
Sent: Wednesday, November 19, 2003 11:15 AM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: RE: [xsl] XSL Tool
Ed, to be honest, I'm not positive I have to use MSXML. My company is
developing asp.net. I am creating html reports from XML that is
generated from out .net apps. We have clients that will be using the
Stylesheet and even altering them. Can I used Saxon? What is the
benefit? How different would setup be for our clients if we used Saxon
as opposed to MSXML?
This communication is intended solely for the use of the addressee and
may
contain information that is legally privileged, confidential or exempt
from
disclosure. If you are not the intended recipient, please note that any
dissemination, distribution, or copying of this communication is
strictly
prohibited. Anyone who receives this message in error should notify the
sender immediately and delete it from his or her computer.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list