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.



Karl..



On 9/2/06, Dimitre Novatchev <dnovatchev@xxxxxxxxx> wrote:
> Looks like I'm moving to 2.0.  F!



Good decision.



Apart form the new XslCompiledTransform class I'd recommend the new
VS2005 (Professional edition and higher) XML Editor and the XSLT
Debugger.





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





On 9/2/06, Karl Stubsjoen <kstubs@xxxxxxxxx> wrote:
> Uggg, have discovered another issue in this release of the .NET XML
> Parser, and that is templates which you attempt to override from the
> base template fail if the template you are trying to write the
> override in is more than 2 deep.
>
> Looks like I'm moving to 2.0.  F!
>
> Karl..
>
> On 9/2/06, Dimitre Novatchev <dnovatchev@xxxxxxxxx> wrote:
> > Yes. This class is new in the .NET Framework version 2.0
> >
> > And the .NET Framework version 2.0 is freely available for download
> > (for example via Windows Update).
> >
> >
> >
> > --
> > Cheers,
> > Dimitre Novatchev
> > ---------------------------------------
> > Truly great madness cannot be achieved without significant intelligence.
> > ---------------------------------------
> > To invent, you need a good imagination and a pile of junk
> >
> >
> >
> >
> > On 9/2/06, Karl Stubsjoen <kstubs@xxxxxxxxx> wrote:
> > > XslCompiledTransform class available only in 2.0?
> > >
> > > On 9/2/06, Dimitre Novatchev <dnovatchev@xxxxxxxxx> wrote:
> > > > This has been resolved in .NET 2.0 -- I cannot reproduce the bug using
> > > > VS2005 XML Editor.
> > > >
> > > > So, simply use the XslCompiledTransform class.
> > > >
> > > >
> > > > --
> > > > Cheers,
> > > > Dimitre Novatchev
> > > > ---------------------------------------
> > > > Truly great madness cannot be achieved without significant intelligence.
> > > > ---------------------------------------
> > > > To invent, you need a good imagination and a pile of junk
> > > >
> > > >
> > > >
> > > >
> > > > On 9/2/06, Karl Stubsjoen <kstubs@xxxxxxxxx> wrote:
> > > > > Hello,
> > > > > I did stumble upon this bug sometime ago:
> > > > > http://www.xslt.com/html/xsl-list/2005-05/msg00476.html
> > > > >
> > > > > Forgot about this, then stumbled upon it again today!  I also found
> > > > > this thread which supports and probably explains the bug better than I
> > > > > did originally:
> > > > > http://groups.google.com/group/microsoft.public.dotnet.xml/browse_thread/thread/653cc56b5a7ca233/7b6c67c43266f6e3%237b6c67c43266f6e3
> > > > >
> > > > > So, frustrating, it appears that the bug still exists!  This is a HUGE
> > > > > problem.  So, is there a known workaround?
> > > > >
> > > > > Karl..
> > >
> > >
> >
> >
> > --
> > Cheers,
> > Dimitre Novatchev
> > ---------------------------------------
> > Truly great madness cannot be achieved without significant intelligence.
> > ---------------------------------------
> > To invent, you need a good imagination and a pile of junk