The immediate child elements of one XElement are accessible by calling the Element() or Elements() functions. Use the overloads with a name to access specific elements, or without to access all child elements. There are also similar methods like Attribute() and Attributes() that you might find useful.
By using XDeclaration. This will add the declaration. But with ToString() you will not get the desired output. You need to use XDocument.Save() with one of his methods. Full sample: var doc = new XDocument( new XDeclaration(“1.0”, “utf-16”, “yes”), new XElement(“blah”, “blih”)); var wr = new StringWriter(); doc.Save(wr); Console.Write(wr.ToString());
There is no need to reparse. One of the constructors of XElement takes another XElement and makes a deep copy of it: XElement original = new XElement(“original”); XElement deepCopy = new XElement(original); Here are a couple of unit tests to demonstrate: [TestMethod] public void XElementShallowCopyShouldOnlyCopyReference() { XElement original = new XElement(“original”); XElement shallowCopy = original; … Read more
As Adam precises in the comment, XName are convertible to a string, but that string requires the namespace when there is one. That’s why the comparison of .Name to a string fails, or why you can’t pass “Person” as a parameter to the XLinq Method to filter on their name. XName consists of a prefix … Read more
To use XPath with LINQ to XML add a using declaration for System.Xml.XPath, this will bring the extension methods of System.Xml.XPath.Extensions into scope. In your example: var value = (string)xml.XPathEvaluate(“/response/data/hash”);
You only need to use the overridden ToString() method of the object: XDocument xmlDoc … string xml = xmlDoc.ToString(); This works with all XObjects, like XElement, etc.
LINQ to XML allows this to be much simpler, through three features: You can construct an object without knowing the document it’s part of You can construct an object and provide the children as arguments If an argument is iterable, it will be iterated over So here you can just do: void Main() { List<string> … Read more
If you want to use namespaces, LINQ to XML makes that really easy: XNamespace ab = “http://whatever-the-url-is”; XElement tempElement = doc.Descendants(ab + “test”).FirstOrDefault(); Look for an xmlns:ab=… section in your document to find out which namespace URI “ab” refers to.
Either explicitly write out the declaration, or use a StringWriter and call Save(): using System; using System.IO; using System.Text; using System.Xml.Linq; class Test { static void Main() { string xml = @”<?xml version=’1.0′ encoding=’utf-8′?> <Cooperations> <Cooperation /> </Cooperations>”; XDocument doc = XDocument.Parse(xml); StringBuilder builder = new StringBuilder(); using (TextWriter writer = new StringWriter(builder)) { doc.Save(writer); … Read more
If you have XDocument it is easier to use LINQ-to-XML: var document = XDocument.Load(fileName); var name = document.Descendants(XName.Get(“Name”, @”http://demo.com/2011/demo-schema”)).First().Value; If you are sure that XPath is the only solution you need: using System.Xml.XPath; var document = XDocument.Load(fileName); var namespaceManager = new XmlNamespaceManager(new NameTable()); namespaceManager.AddNamespace(“empty”, “http://demo.com/2011/demo-schema”); var name = document.XPathSelectElement(“/empty:Report/empty:ReportInfo/empty:Name”, namespaceManager).Value;