HasChildNodes does not work properly

Brian · Dec 15, 2003

? nChild.OuterXml
"<LocaleId>{76135713-CB5C-4116-925F-1E69254A775B}</LocaleId>"

? nChild.HasChildNodes
True

TEXT IS NOT A NODE!!!

Please explain.

TIA -
Brian

Jay B. Harlow [MVP - Outlook] · Dec 15, 2003

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/d...pref/html/frlrfSystemXmlXmlTextClassTopic.asp

Check the XmlNodeType enumeration, Text is listed as a node type.
http://msdn.microsoft.com/library/d.../html/frlrfSystemXmlXmlNodeTypeClassTopic.asp

Hope this helps
Jay

Brian · Dec 16, 2003

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

Cor · Dec 16, 2003

Hi Brian

In addition to Jay B.

Have a look at "innertext" and "innerHtml"

I hope this helps

Cor

HasChildNodes does not work properly

Brian

Jay B. Harlow [MVP - Outlook]

Brian

Cor