.net Xslt Engine

[falik]

Hello, I need some advice in choosing appropriate processor to include to my AHFormatter. I have to do some crazy stuff with images and there's no way to do it in xslt so I have to implement a function in C# to do these.The problem is that my Formatter has MSXSL 3.0 included, and this xslt engine supports only scripts in JScript or VBScript and those don't offer me necessary functions. In C# I got some Image libraries that would do the job. The problem is that I actually don't know what other xslt engine should I use. The ones I know is Saxon and AltovaXML and I don't know anything about their possibilities.I would appreciate any help.

[Martin Honnen]

.NET (2.0 and later) has a built-in XSLT 1.0 processor with System.Xml.Xsl.XslCompiledTransform, documented at http://msdn.microsoft.com/en-us/library/0610k0w4.aspx. That documentation has a section on extending stylesheets: http://msdn.microsoft.com/en-us/library/6datxzsd.aspx.For the XSLT 2.0 processors you named the documentations are http://www.saxonica.com/documentation/extensibility/integratedfunctions.xml respectively http://manual.altova.com/AltovaXML/altovaxmlreporting/index.html?xextnet.htm (only available in the commercial version I think, no longer in the free version).There is also a third commercial XSLT 2.0 implementation for .NET, XQSharp: http://www.xqsharp.com/

[falik]

The problem is that I'm not supposed to use XSL in .NET but .NET in XSL. So u say that there's no possibillity to do what I want on freeware, only with those commercial versions of processors yes ?

[Martin Honnen]

The problem is that I'm not supposed to use XSL in .NET but .NET in XSL. So u say that there's no possibillity to do what I want on freeware, only with those commercial versions of processors yes ?

No, XslCompiledTransform is part of .NET as delivered by Microsoft and it has the extension features I pointed you to. And the open source version of Saxon also allows what is called integrated extension functions. For AltovaXML it seems as if at least the latest release only allows extensions written in .NET with the commercial version. For XQSharp there is only one version you seem to be allowed to use for non-commercial purposes: http://www.xqsharp.com/xqsharp/licensing.htm#non-commercial.

[falik]

Unfrotunately I think that I didn't understand u clearly... This is what I do: I write xslt and xsl-fo in one xsl stylesheet ---> i open AHFormatter ---> I do the transformationThat script embedding that u are talking about is this I think: http://msdn.microsoft.com/en-us/library/533texsx(vs.71).aspxBut it considers the transformation to be done rather much like: I write xslt and xsl-fo in one xsl stylesheet with scripts ---> transform within C# code using .NET ---> put the result in AHFormatter When I was doing some Jscript's I could just put them in <script> tags and just do it with AHFormatter, using an outer C# app is not what I would like.If I am wrong with those script embedding and the C# scripts can be embed just as JScript, correct me please.

[Martin Honnen]

I don't know what AHFormatter is, ask in a forum dedicated to that tool if you need help in using it with a different XSLT processor.