IIRC, The .NET 2.0 XslCompiledTransform does not pass the params to subsequent matches in the hierarchy, only to the first match, if you're using a wide scoped <xsl:apply-templates /> instead of providing it a specific nodeset to work on. To be more specific, I think we'll need to see a (simplified version) of your XSLT and the XML.
On Apr 10, 9:53 pm, Liliths Thrall <[email protected]> wrote: > I've got an XSLT stylesheet. It has many different calls to apply- > templates. These apply-templates calls pass params to their related > templates. > Pretty garden variety really. > But .NET 2.0 is throwing an error that the params are undefined or out > of scope. > Now, the stylesheet works correctly in XML Spy. So, I'm wondering if > there is a known bug in .NET 2.0 XmlCompiledTransform/XPathDocument > that causes it to have scoping problems for parameters passed via > apply-templates? If so, is there a known work around or patch? I'm > dealing with a -lot- of data, the last thing I want to do is rewrite > the stylesheet as some sort of imperative programming hack.
