limitations with XslCompiledTransform and Xpath predicates

I've found out (from an XslLoadException) that Xpath predicates can't be used in template match statements with XslCompliedTransform. I can use predicates in xsl:for-each statements without getting an exception but it still doesn't work correctly. Non .net implementations seem to have no problems with using Xpath predicates. I can't find any docs on XslCompiledTransform's support for Xpath predicates. Does anyone know what the limitations are?
[458 byte] By [ClintStotesbery] at [2008-2-25]
# 1
Please provide your stylesheet, because I just tried a simple template with a predicate like this and it works fine.

<xsl:template match="item[@id > 10]">
<
xsl:copy-of select="."/>
</
xsl:template>

ChrisLovett at 2007-9-9 > top of Msdn Tech,.NET Development,XML and the .NET Framework...
# 2
Looks like the problem is with using params with predicates in a template match statement. See the example files at:
http://mavweb.mnsu.edu/stotec1/example.zip
I get an XslLoadException using that example.
ClintStotesbery at 2007-9-9 > top of Msdn Tech,.NET Development,XML and the .NET Framework...
# 3
Unfortunately XSLT 1.0 doesn't allow variables or params to be used in match patterns. Usually a problem can be solved by moving selection logic to xsl:apply-templates.
OlegTkachenko at 2007-9-9 > top of Msdn Tech,.NET Development,XML and the .NET Framework...

.NET Development

Site Classified