http://blogs.msdn.com/b/antosha/Secrets of using XML and XSLT in the .NET worlden-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/antosha/archive/2007/05/28/xsltc-compile-xslt-to-.net-assembly.aspxTue, 29 May 2007 03:13:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:2955402antosha2http://blogs.msdn.com/b/antosha/rsscomments.aspx?WeblogPostID=2955402http://blogs.msdn.com/b/antosha/archive/2007/05/28/xsltc-compile-xslt-to-.net-assembly.aspx#commentsIn 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...(<a href="http://blogs.msdn.com/b/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">XSLTSystem.XmlXslCompiledTransformhttp://blogs.msdn.com/b/antosha/archive/2006/07/24/xslcompiledtransform-performance-beating-msxml-4-0.aspxMon, 24 Jul 2006 15:29:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:677560antosha5http://blogs.msdn.com/b/antosha/rsscomments.aspx?WeblogPostID=677560http://blogs.msdn.com/b/antosha/archive/2006/07/24/xslcompiledtransform-performance-beating-msxml-4-0.aspx#comments<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/b/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">XSLTMSXMLSystem.XmlXslCompiledTransformhttp://blogs.msdn.com/b/antosha/archive/2006/07/16/xslcompiledtransform-slower-than-xsltransform.aspxSun, 16 Jul 2006 17:40:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:667221antosha0http://blogs.msdn.com/b/antosha/rsscomments.aspx?WeblogPostID=667221http://blogs.msdn.com/b/antosha/archive/2006/07/16/xslcompiledtransform-slower-than-xsltransform.aspx#commentsThe .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/b/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">XSLTSystem.XmlXslCompiledTransform