That's helpful, but one question remains: does updating a node in an
XmlNodeList returned from SelectNodes cause a "live" update to the
XmlDocument?

The Help from SelectNodes says "...changes that appear in the XML diocument
may not appear in the XmlNodeList, and vice versa." "Vice versa" implies to
me that if you make changes to the XmlNodeList, you can't count on them being
reflected in the XmlDocument.

And yet the code example from the same Help entry (see below) does exactly
that - it changes nodes in a NodeList returned from SelectNodes, and then
writes out the XmlDocument (expecting it to have been changed).

Any insight?

----------------------------------------
using System;
using System.IO;
using System.Xml;

public class Sample {

public static void Main() {

XmlDocument doc = new XmlDocument();
doc.Load("booksort.xml");

XmlNodeList nodeList;
XmlNode root = doc.DocumentElement;

nodeList=root.SelectNodes("descendant::book[author/last-name='Austen']");

//Change the price on the books.
foreach (XmlNode book in nodeList)
{
book.LastChild.InnerText="15.95";
}

Console.WriteLine("Display the modified XML document....");
doc.Save(Console.Out);

}
}

"Martin Honnen" wrote:

Short answer: yes

Long answer: there is but one 'node' SelectNodes does not return a
copy, or some view, it returns the actual node.


I believe the help is trying to indicate that changes to the document
may not cause nodes to be added/removed from the XmlNodeList result of
SelectNodes. For example, if I select "//foo[@a=1]" (all elements
'foo' inthe null namespace with attribute 'a' with value '1'), then if
I change the value of an 'a' attribute on a 'foo' element, that
may-or-may-not result in a change to the nodes reported by the
XmlNodeList.

-derekdb

Tom G wrote: