Because if you traverse the tree using FIRSTCHILD and NEXTSIBLING, you
do not get the text type nodes, only the element type nodes.
Make sense? If a Node can be text, attribute, etc. (which I know from
my XSLT coding) then why does NEXTSIBLING jump to the next text node?
It should be called "NextSiblingElement"?
Thanks,
Brian
"Jay B. Harlow [MVP - Outlook]" <Ja************@msn.com> wrote in message news:<Oo**************@TK2MSFTNGP11.phx.gbl>...
Brian, TEXT IS NOT A NODE!!!
Actually Text IS a type of Node! May I ask why you think it is not?
Check the hierarchy of the XmlText class, it inherits from XmlNode like all
the other nodes.
http://msdn.microsoft.com/library/de...ClassTopic.asp
Check the XmlNodeType enumeration, Text is listed as a node type.
http://msdn.microsoft.com/library/de...ClassTopic.asp
Hope this helps
Jay
"Brian" <bo***@vafb.com> wrote in message
news:d2**************************@posting.google.c om... ? nChild.OuterXml
"<LocaleId>{76135713-CB5C-4116-925F-1E69254A775B}</LocaleId>"
? nChild.HasChildNodes
True
TEXT IS NOT A NODE!!!
Please explain.
TIA -
Brian