Re: Confirmimg - Bug in Accessing Global XSL Variables

I hate to say this, but I still think there is a problem here.
Possibly I am doing something wrong so not real confident at the
moment.

It appears that the global variable problem has been fixed in .NET 2.0
using the XslCompiledTransform Class.  However, what is not fixed is
the use of global templates.

There does not appear to be a problem if the global template is named
without a namespace, but as soon as you introduce a namespace, the
call fails.

There is not a problem if the template is defined in the immediate
imported base template, but when the defined template is 2 deep.

Please confirm.

Could you, please, provide an (the shortest possible but complete)
example that demonstrates the problem you're having?

--
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
---------------------------------------
To invent, you need a good imagination and a pile of junk