XSL tranforms in .NET

[AtW]

Xsl transform functions is clearly a badly written piece of code, strange as it seems to be written by Russians ...

Shimano - chew your gum dude...

[DimPrawn]

Have a look see if this is any better

http://saxon.sourceforge.net/

[AtW]

4.8 MB .NET distribution?

No, a hybrid solution was proposed - query object using XPath and then pass that XML to XSL template, it better fking work!

[HankWangford]

mvp.xml

4.8 MB .NET distribution?

No, a hybrid solution was proposed - query object using XPath and then pass that XML to XSL template, it better fking work!

also check out the mvp xml project, they like wraping and increasing the performance of the frameworks xml/xsl methods http://sourceforge.net/projects/mvp-xml/

[mcquiggd]

Alexei....

Check out this....

http://blogs.msdn.com/xmlteam/articl...Transform.aspx

Although marked as 'unfinished' it does seem to back yup your observation ... executing the transform is performed using an XmlReader that traverses the whole document.


"Performing the Transformation
Once the stylesheet is fully loaded, XslCompiledTransform can transform the input document. Transformation of the input document to output involves the following steps:

Parsing the input document and building an in-memory XML tree representation for it.
Transforming the input XML tree to the output tree.
Serialization of the output tree.
To load the cache, XslCompiledTransform uses XmlReader to read the input document. At this time, XslCompiledTransform applies whitespace stripping rules.
"

[DimPrawn]

The problem is all this dodgy code written by Russians:

Authors: Sergey Dubinets, Anton Lapounov

[mcquiggd]

Bah! Why didn't they employ Polish chappies like what we do like....