R
Ryan Liu
Hi,
I know I need create a DataRow from a DataTable for the schema reason.
Why must I create a XmlElement in a XmlDocument?
I already have a string, I was trying to use XmlDocument.CreateElement("Q")
method to create a "fake" or "Empty" XmlElement and set this element's
OuterXml, but OuterXml is read only.
I can set inner Xml, but I think I will lost attributs of element Q. I will
try that out.
But what is best practice to create an element from a given complete node
string? Should I try ImportNode()?
And same as new DataRow does not belong to DataTable, after I create the
element, it is not part of the XmlDocument unless I append to one of its
chile node, right?
Microsoft SDK is great resouce, but some time I still feel it tells
something, but not deep and clear enough, I need write small test programs
and ask others to know what really is its accurate meaning.
Thanks a lot!
Ryan
I know I need create a DataRow from a DataTable for the schema reason.
Why must I create a XmlElement in a XmlDocument?
I already have a string, I was trying to use XmlDocument.CreateElement("Q")
method to create a "fake" or "Empty" XmlElement and set this element's
OuterXml, but OuterXml is read only.
I can set inner Xml, but I think I will lost attributs of element Q. I will
try that out.
But what is best practice to create an element from a given complete node
string? Should I try ImportNode()?
And same as new DataRow does not belong to DataTable, after I create the
element, it is not part of the XmlDocument unless I append to one of its
chile node, right?
Microsoft SDK is great resouce, but some time I still feel it tells
something, but not deep and clear enough, I need write small test programs
and ask others to know what really is its accurate meaning.
Thanks a lot!
Ryan