Its the implementor!!! (sorry). I found the problem, one of my
namespace declerations was wrong. The good news: I've leaped into
2.0!
Thanks,
Karl..
On 9/3/06, Dimitre Novatchev <dnovatchev(_at_)gmail(_dot_)com> wrote:
On 9/3/06, Karl Stubsjoen <kstubs(_at_)gmail(_dot_)com> wrote:
> Dimitre, I will see if I missed something or misrepresented the code I
> have. Indeed I have some sort of problem, it may be the implementer.
Yes, and just FYI, the same transformation is performed perfectly OK
with XslTransform (.Net1.1).
Cheers,
Dimitre Novatchev
---------------------------------------
Truly great madness cannot be achieved without significant intelligence.
---------------------------------------
To invent, you need a good imagination and a pile of junk
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--