xmlNode.RemoveChild is removing xmlNode...not the child node

[WebDunce]

Hi guys,

I am trying to develop a simple xml editor. I have an object that has a TreeView. I use the TreeView to display the Xml node info. That's all fine, but i want the user to be able to move the actual xml nodes about by interacting with the non-xml TreeView nodes.

my basic algorithm is as follows:

• user has selected a treeview node
• if user presses Ctrl+Up Arrow, then
  • clone the corresponding xml node
  • remove the xml node
  • insert the xml node CLONE into the parent xml
    node's child list BEFORE the node that was
    above the node to start with

the treeview nodes are working just right...but to my dismay, when remove the selected xml node...the parent also disappears!

basically, I am doing this...

Dim nodeToRemove As XmlNode =  Me.xmlDoc.SelectSingleNode("//page[@id=/website/@currentPageId]")
Dim parentNode As XmlNode = nodeToRemove.ParentNode
parentNode.RemoveChild(nodeToRemove)
 

this is removing parentNode...and i cant figure out why!

any ideas?

thanks in advance.

[WebDunce]

okay...a little more research produces some insight...

'xmlDoc is an XmlDocument object
 
 Dim nodeToRemove As XmlNode = Me.xmlDoc.SelectSingleNode("//page[@id=/website/@currentPageId]")
 Dim parentNode As XmlNode = nodeToRemove.ParentNode
 'parentNode.RemoveChild(nodeToRemove)
 MainForm.TextBox1.Text = nodeToRemove.InnerXml
 

nodeToRemove.InnerXml is displaying the node i think i am selecting plus all siblings

nodeToRemove.OuterXml is displaying what i would consider to be the parent node.

what am i missing here...how can i select a single node (why doesn't SelectSingleNode select the single node?)
thanks.

[kenobewan]

I believe that you need to reference the child node in the remove, something like:

XmlNode.RemoveChild(XmlNode.SelectSingleNode("ChildNode"))

[WebDunce]

hi KenObeWan,

i appreciate the response, but i think i tried every which way to reference the node...all with the same results. however, i think i found the problem...and it wasn't with the SelectSingleNode method at all...like i originally thought.

turns out...SelectSingleNode is working just like it should (surprise, surprise, surprise)...i just wasn't feeding it the info i THOUGHT i was giving it...

turns out my code (somewhere) is not updating the attribute value (/website/@currentPageId) like i am thinking it is...

when i reference that attribute value like so:

nodeToRemove = Me.xmlDoc.SelectSingleNode("//page[@id=/website/@currentPageId]")
 

i get the parent node not the node i am wanting...

but when i hardcard the page id value like so:

nodeToRemove = Me.xmlDoc.SelectSingleNode("//page[@id='0018']")
 

then it works...i get the node i am expecting.

now to find out why the attribute value is not updating like i thought i told it to...(sigh)...but at least now i know what is wrong and my confidence is restored in the SelectSingleNode method.

thanks for letting me post...even if it turned out i simply answered myself...:) sometimes it helps just to write the problem out. And posting it publicly encourages me to try even harder to come up with a solution, too.

cheers all.

[WebDunce]

ahem..."hardcard" = "hardcode" oops!

[kenobewan]

Well done - shows that you are no dunce ;). Thanks for sharing the solution.