Validating xml against Free cybersex chat bots
From one perspective you can think of LINQ to XML as a member of the LINQ Project family of technologies with LINQ to XML providing an XML Language-Integrated Query capability along with a consistent query experience for objects, relational database (LINQ to SQL, LINQ to Data Set, LINQ to Entities), and other data access technologies as they become LINQ-enabled.
From another perspective you can think of LINQ to XML as a full feature in-memory XML programming API comparable to a modernized, redesigned Document Object Model (DOM) XML Programming API plus a few key features from XPath and XSLT.
For example using Xml Document (the DOM implementation from Microsoft) this would be a typical way to create an XML tree. Inner Text = "206-555-0144"; Xml Element phone2 = doc. XDocument contacts Doc = new XDocument( new XDeclaration("1.0", "utf-8", "yes"), new XComment("LINQ to XML Contacts XML Example"), new XProcessing Instruction("My App", "1"), new XElement("contacts", new XElement("contact", new XElement("name", "Patrick Hines"), new XElement("phone", "206-555-0144"), new XElement("address", new XElement("street1", "123 Main St"), new XElement("city", "Mercer Island"), new XElement("state", "WA"), new XElement("postal", "68042") ) ) ) ); XML names LINQ to XML goes out of its way to make XML names as straightforward as possible.
Xml Document doc = new Xml Document(); Xml Element name = doc. Inner Text = "Patrick Hines"; Xml Element phone1 = doc. Arguably, the complexity of XML names, which is often considered an advanced topic in XML literature, comes not from namespaces, which developers use regularly in programming, but from XML prefixes.
LINQ to XML was developed with Language-Integrated Query over XML in mind from the beginning.
Net Framework 3.5 Summary: LINQ to XML was developed with Language-Integrated Query over XML in mind and takes advantage of standard query operators and adds query extensions specific to XML.
This section details how to program with LINQ to XML independent of Language-Integrated Query. In DOM XML nodes, including elements and attributes, must be created in the context of an XML document.
Because LINQ to XML provides a fully featured in-memory XML programming API you can do all of the things you would expect when reading and manipulating XML. Here is a fragment of the code from the previous example to create a name element: Note how the XML document is a fundamental concept in DOM.
In LINQ to XML, an XName represents a full XML name consisting of an XNamespace object and the local name. In contrast, the W3C DOM always treats text as an XML node.
Developers will usually find it more convenient to use the XNamespace object rather than the namespace URI string. Consequently in many DOM implementations the only way to read and manipulate the underlying text of a leaf node is to read the text node children of the leaf node.