3.3.
Convert Underperforming XSL Renderings to .NET
Certain operations can be completed much more efficiently in .NET than in XSL. Use Sitecore’s browser-based debugger to identify poorly performing code for migration to pure .NET.
Invoking XSL may be more expensive in .NET than executing native .NET code. If possible, certain XSL renderings, especially those which consume a great deal of resources or can only be cached under limited conditions should be converted to .NET method renderings, sublayouts or web controls. Expensive XSL code can be converted to .NET extension controls and functions.
Mark Ursino on 07 Oct 10Converting objects from one type to another is a common practice in software development. When dealing with this, it is important to understand the difference between standard casting and using the "as" operator to convert. In this article, Brendan explains this difference and when to use each type of conversion. His code snippets demonstrate the information he is explaining in the article.
