In a previous post we announced the release of the new BizTalk 2013, listing all of the new features it will bring. In the upcoming posts I would like to explain in more detail some of these features, and the consequences it will bring with it.
First of all, one of the changes introduced in BizTalk 2013 is the use of the enhanced XslCompiledTransform API, instead of using the XslTransform API that is used in older BizTalk versions. This change would provide significant improvements in mapping engine performance for complex maps. Sounds great, but what is the difference between both?
First of all, I would like to note that the XslTransform API has become obsolete and has been replaced by XslCompiledTransform.
The new XslCompiledTransform API will boost the performance for complex maps. Although I would like to make a side note about this one… Although the overall performance of the XslCompiledTransform class is better than the XslTransform class, the Load method of the XslCompiledTransform class might perform more slowly than the Load method of the XslTransform class the first time it is called on a transformation. This is because the XSLT file must be compiled before it is loaded. For more information, see the following blog post: XslCompiledTransform Slower than XslTransform?
Using the XslCompiledTransform will compile the XSLT style sheet down to a common intermediate format. And once the style sheet is compiled, it can be cached and reused. Making the XslCompiledTransform considered the best choice for the “one