Secrets of using XML and XSLT in the .NET worldhttp://blogs.msdn.com/antosha/atom.xmlCommunity Server2006-07-16T07:40:00Zhttp://blogs.msdn.com/antosha/archive/2007/05/28/xsltc-compile-xslt-to-.net-assembly.aspx2007-05-29T03:13:00Z2007-05-29T03:13:00ZIn my two previous posts I described a potential performance hit caused by XSLT-to-MSIL compilation and JIT-compilation when you load and run some XSLT stylesheet with the XslCompiledTransform engine for the first time. Since the .NET Framework 2.0 did not allow you to save compiled stylesheets, you had to pay the compilation price on each application run. XSLT Compiler Utility The good news is we are providing the XSLT Compiler command-line utility xsltc.exe (announced here ) that can be used to...(<a href="http://blogs.msdn.com/antosha/archive/2007/05/28/xsltc-compile-xslt-to-.net-assembly.aspx">read more</a>)<img src="http://blogs.msdn.com/aggbug.aspx?PostID=2955402" width="1" height="1">antoshahttp://blogs.msdn.com/members/antosha.aspxhttp://blogs.msdn.com/antosha/archive/2006/07/24/xslcompiledtransform-performance-beating-msxml-4-0.aspx2006-07-24T15:29:00Z2006-07-24T15:29:00Z<p>Interestingly enough, the first <a href="http://live.com">live.com</a> hit for the "XslCompiledTransform Performance" query at the moment is <a href="http://www.wintellect.com/Weblogs/XslCompiledTransformPerformance.aspx">this post</a> of Jeff Prosise, where he says he was disappointed that <code>XslCompiledTransform</code> ran just 3 times faster than <code>XslTransform</code> on a "fairly simple style sheet". He is concerned that <code>XslCompiledTransform</code> is not fast enough comparing to the good old MSXML 4.0. Well, as we will see very soon, <code>XslCompiledTransform</code> may easily outperform MSXML 4.0 by several times!</p>...(<a href="http://blogs.msdn.com/antosha/archive/2006/07/24/xslcompiledtransform-performance-beating-msxml-4-0.aspx">read more</a>)<img src="http://blogs.msdn.com/aggbug.aspx?PostID=677560" width="1" height="1">antoshahttp://blogs.msdn.com/members/antosha.aspxhttp://blogs.msdn.com/antosha/archive/2006/07/16/xslcompiledtransform-slower-than-xsltransform.aspx2006-07-16T17:40:00Z2006-07-16T17:40:00ZThe .NET Framework 2.0 provides a new <A href="http://msdn2.microsoft.com/en-us/library/system.xml.xsl.xslcompiledtransform.aspx"><CODE>System.Xml.Xsl.XslCompiledTransform</CODE></A> XSLT processor class, which is intended to replace the obsoleted <CODE>XslTransform</CODE> class. One of the major differences between the two is that while the latter is an XSLT <A href="http://en.wikipedia.org/wiki/Interpreter_%28computing%29">interpreter</A>, the former is a real XSLT <A href="http://en.wikipedia.org/wiki/Compiler">compiler</A>, allowing significantly faster execution times. Does it mean <CODE>XslCompiledTransform</CODE> is always faster? Surprisingly, the answer is not that simple....(<a href="http://blogs.msdn.com/antosha/archive/2006/07/16/xslcompiledtransform-slower-than-xsltransform.aspx">read more</a>)<img src="http://blogs.msdn.com/aggbug.aspx?PostID=667221" width="1" height="1">antoshahttp://blogs.msdn.com/members/antosha.aspx