One of the problems I encounter is versioning xslt for MSXML and System.Xml.Xsl. Here is a post that shows a way to detect the xslt engine: http://www.tkachenko.com/bl... <!--StartFragment-->&... version="1.0" xmlns:xsl="http://www.w3.or... xmlns:ms="urn:schemas-micro... exclude-result-prefixes="ms... <xsl:template match="/"> <p> This XSLT stylesheet is being executed using <xsl:choose> <xsl:when test="system-property('xsl:... ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/Vg0

One of the new features in the Visual Studio 2008 release is the XSLT Compiler tool xsltc.exe. The documentation can be found here. This tool will precompile the xslt sheets into an assembly. It has been my experience over the years that the xsl mappings change more often than the message flows. With the xsltc.exe tool the mappings can be changed, compiled and installed without changing the Biztalk orchestrations. First you need to create the xsl DLLs: xsltc.exe /settings:document+,script+ myXsl.xsl ......

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/VTc