Changed the way XElement was done through .Add and got what he wanted. XElement onEvent = new XElement("onEvent",task_name.Text.ToString()); onEvent.Add(new XAttribute("type", EventType.Text.ToString())); onEvent.Add(new XAttribute("status", EventStatus.Text.ToString())); dialog.Add(onEvent); XElement name = new XElement("name", Dialog_name.Text.ToString()); dialog.Add(name); XElement dissposable = new XElement("dissposable", testT); dialog.Add(dissposable); foreach (Phrase element in EndArray) { XElement replic = new XElement("replic"); XElement character = new XElement("character", element.get_char(element)); replic.Add(character); XElement message = new XElement("message", element.get_phrase(element)); replic.Add(message); dialog.Add(replic); }

In general, as it appeared during the comparison of the results of the insertion in the table, the structure transferred to the table was not a insertion but a sequence of the addition of parameters. Why don't I know that, I' look for information.

All right, explain the situation - first we need to check the presence of the Beremenice Node, see if there's an element in it.

You will first decide how the user will be more comfortable watching and editing these data. You can put it in one table, you can get a few.For example, all xml can be loaded DataSet by ReadXml:var dataSet = new DataSet(); dataSet.ReadXml("test.xml"); There will be three tables on the date of the visit: PRODUCT, PRICES (vasible, not to be shown to the user) and PRICE (with area columns and PRICE_text).These tables are simpler, tied to them. DataGridView:dataGridView.DataSource = dataSet.Tables[0]; If there is no need for any columns, you can hide them; the headings can be renamed:dataGridView.DataSource = dataSet.Tables[2]; dataGridView.Columns["area"].Visible = false; dataGridView.Columns["PRICE_text"].HeaderText = "Price"; The problem is, if the user is right in. DataGridView add new lines, if data are retained by the method DataSet.WriteXml There's no way the lines could come out where they want. So there's a new table. This method is therefore only appropriate for the data, without editing.

var items=(from xe in fdoc.Element("Groups")?.Elements("Group") where xe.Element("Name").Value.Equals(str) select (from xel in xe.Elements("User") select xel.Value).ToList()); However, such a request would return IEnumerable<List<String>> because a list of the user values will be returned to each type of group element.If your name filter should return one value (or nothing at failure) add FirstOrDefault()var items=(from xe in fdoc.Element("Groups")?.Elements("Group") where xe.Element("Name").Value.Equals(str) select (from xel in xe.Elements("User") select xel.Value).ToList()).FirstOrDefault(); The result of this request will be List<String>To verify that the name is unique, you can use the SingleOrDefault method, then the exception will be waived if there are several elements with the name sought.

Instead of a sample of all tags:doc.Descendants() We need to pick the tages inside. <ttt>and leave only unique:doc.Descendants() // выбираем все тэги .Where(x => x.Name == "ttt") // выбираем среди них тэги ttt .SelectMany(x => x.Descendants()) // выбираем тэги внутри ttt .Select(x => x.Name).Distinct() // выбираем уникальные имена Total:var tagNames = doc.Descendants() .Where(x => x.Name == "ttt") .SelectMany(x => x.Descendants()) .Select(x => x.Name) .Distinct(); // опционально можно отсортировать // tagNames = tagNames.OrderBy(x => x.LocalName); foreach (var x in tagNames) listBox1.Items.Add(x);

Open the opening. try/catch♪All statistical ways of working with XML are dispensed with non-qualification (in the sense of well-formed) of the document. Methods IsWellFormed No.The only thing that can be improved (if you haven't already done) is to use for validation. XmlReader c https://msdn.microsoft.com/en-us/library/system.xml.xmlreadersettings.validationflags(v=vs.110).aspx - to avoid potential problems with the huge papers that the battles are at the end.

On the one hand, you might think that interfaces initiated in the cycle foreach and the idea cannot be unpropriized (and that's true). But on the other hand, the compiler can't know exactly what's in the variable. intf there's something to irritate by foreach (in other words, he does not know if the cycle will be implemented at least once). It turns out there's a situation where your variable is possible. interfaces I'm gonna stay uninitiated, and that's why the compiler signals the error. In fact, the theoretical developers of the compilator could have had a breathing and compiling compiler to analyse such designs and predict the behaviour of the cycle (when it is obvious to a person, the compiler could have understood it even better), but they probably did not complicate themselves and the compilator of the work and simply forced him to give a report on the protection, including in such an obvious situation.public static void Create_Interfaces() { var interfaces = new XDocument(new XElement("Interfaces", new XElement("Interface", new XElement("vlan-tagging", XElement.EmptySequence), new XElement("unit", new XElement("vlan-id", "10"), new XElement("family", new XElement("inet", new XElement("address", new XElement("name", "10.10.1.23/24")))))))); ; var intf = new List<string> { "em0", "em1", "em2" }; foreach (var i in intf) interfaces.Element("Interfaces").Element("Interface").AddFirst(new XElement("name", i)); interfaces.Save("Interfaces.xml"); }

The announcement of the area of the name extends to all the elements that have been invested.You made a knot. kml with hermspeace: aw + "kml♪ They'. <kml xmlns="http://www.opengis.net/kml/2.2">♪But the knot. Document You create a name without space. So he doesn't belong to this nemspeis, which means he's referring to an empty area of the name. It is therefore automatically added. xmlns=""♪If the file says:<kml xmlns="http://www.opengis.net/kml/2.2"> <Document> That would mean both knots without prefix: kml and Document belongs to the same area of the name.If that's what you need, the decision will be as follows:XElement kml = new XElement(aw + "kml"); XElement document = new XElement(aw + "Document"); XElement name = new XElement(aw + "name", "Моя карта"); We're adding nemspice to all elements. aw♪There's a shorter form of recording of the creation of xml:var xdoc = new XDocument( new XElement(aw + "kml", new XElement(aw + "Document", new XElement(aw + "name", "Моя карта") ))); It's recommended that it be used.Recommended http://zvon.org/comp/r/tut-Namespace.html#intro (please put the reference in the Next) to zvon.org. It's good, in the flowers, it shows which nodes are to which area the names belong.I'd like the formatting there. ♪ ♪Yeah, there is. http://zvon.org/xxl/NamespaceTutorial/Output/example1.html with normal formatting.

You can do this:using System; using System.Linq; using System.Xml.Linq; namespace ConsoleApplication7 { class Program { static void Main() { var e1 = XElement.Parse("<e1 xml:lang='en-us'><e2></e2></e1>"); ; var e2 = e1.Element("e2"); var attr = e2.AncestorsAndSelf().Attributes(XNamespace.Xml + "lang").First(); Console.WriteLine("n2.XmlLang: {0}", attr.Value); } } }

So, the solution.[barabab throttle]XNamespace(!)facepalmDecision and discussion https://stackoverflow.com/questions/14811639/receiving-error-code-value-from-xml-file

Thank you for your decision.The problem was that different platforms had been installed different cultures.It was in the method. double.TryParse()if (double.TryParse(sKey, out key)) //Windows принимает числа формата 3.5, а iOS - нет { if (double.TryParse(sValue, out value)) { boundaries.Add(key, value); //Эти строчки не выполнялись на iOS, ибо double.TryParse() возвращал false } } Addressing the problemSystem.Globalization.NumberStyles numberStyles = System.Globalization.NumberStyles.Any; System.Globalization.CultureInfo cultureInfo = System.Globalization.CultureInfo.InvariantCulture; foreach(var element in boundariesElements) { string sKey = element.Attribute("Key").Value; string sValue = element.Attribute("Value").Value; if (double.TryParse(sKey, numberStyles, cultureInfo, out key)) { if (double.TryParse(sValue, numberStyles, cultureInfo, out value)) { boundaries.Add(key, value); } } }

He was on his knee. Supports a single record and the addition of a new node:string[] array = {"Sasha", "Masha", "Natasha"}; foreach (string username in array) { Boolean exists = File.Exists("data.xml"); XDocument xdoc = exists ? XDocument.Load("data.xml") : new XDocument(); XElement list = exists ? (xdoc.Element("users") == null ? new XElement("users") : xdoc.Element("users")) : new XElement("users"); XElement user = new XElement(username); XAttribute timeto_ = new XAttribute("TimeTo", DateTime.Now.ToString("dd.MM.yyyy, HH:mm:ss")); user.Add(timeto_); XAttribute chatid_ = new XAttribute("chat_id", "1"); user.Add(chatid_); if (list.HasElements) list.AddFirst(user); else list.Add(user); if (exists) xdoc.ReplaceNodes(list); else xdoc.Add(list); xdoc.Save("data.xml"); MessageBox.Show("Added: " + username); } Result (final):<?xml version="1.0" encoding="utf-8"?> <users> <Natasha TimeTo="17.06.2018, 15:11:24" chat_id="1" /> <Masha TimeTo="17.06.2018, 15:11:23" chat_id="1" /> <Sasha TimeTo="17.06.2018, 15:11:22" chat_id="1" /> </users> So the author did not describe the substance of his code. Maybe there's a lot to throw out or something to add. A very good description of the work with XML documents in the examples of code and result for https://metanit.com/sharp/tutorial/16.2.php for https://metanit.com/sharp/tutorial/16.5.php ♪

If the purpose is to do everything in Linq to XML, the characteristics of the elements are an obvious analog of the attributes. Which means they can be treated the same way as attributes:new Document( new ColorProperty(Yellow), new Span("Title", new ColorProperty(White)), new Grid() { // ... очень длинный документ } new Span("Footer") ) However, I don't think Linq to XML is the API understanding reference, but it's not necessary to do everything there is. In the end, there are more generic options in C# to do the same:new Document { Color = Yellow, Children = { new Span("Title") { Color = White }, new Grid { }, "Footer", }, } The properties attached may be similarly:new Span("Foo") { AttachedProperties = { { Grid.ColumnProperty, 1 }, }, } I recall that for the use of the Collection Initializer in C#, the type must have the method of adding and implementing the IEnumerable interface, the two requirements being in no way related to each other: an arbitrary amount of overloading of the method of adding with any number of parameters and any type of parameters.

And if so:XmlDocument.CreateElement("prefix", "name", "uri"); //для элементов new XAttribute(XNamespace.Xml + "space", "preserve"); //для атрибутов

There you go.List<Something> entities = (from node in document.Descendants("Something") select new Something(node.Attribute("id").Value, node.Attribute("name").Value)).ToList(); To get to the attributes, use it. http://msdn.microsoft.com/ru-ru/library/system.xml.linq.xelement.attribute

You need to create a class. Person with FIO properties.Create class. Repository with methods for recording/reading xml file.Start reading xml file List<Person> People and assign it as ListBox.ItemsSource♪Create properties public Person SelectedPerson { get; set; } and make this characteristic relevant to ListBox.SelectedItemThen when you choose the list, you'll have a change and you'll be able to extract the name and show it. Label♪ It's a general description, a lot of different newances.

Anything. For example, if you want to add one, it's like:var lastQuestionNumbers = doc.Descendants("questionNumbers").Last(); lastQuestionNumbers.AddAfterSelf( new XElement("questionNumbers", new XAttribute("numbers", TotalQuestions), new XElement("question" + TotalQuestions, new XAttribute("text", Question), new XAttribute("true", TrueAnswer), new XElement("answer", "5"))));

C XDocument It will not be possible to keep the entire document in mind. If you need to read the information, you need to use it. XmlReaderit's flux.Like finding everything. str_Namerelevant to this int_ESRThat's the code.var goodEsrValues = new HashSet<string>( stationValid.Select(station => station.ESR.ToString())); using (TextReader tr = ...) using (var reader = XmlReader.Create(tr)) { while (reader.Read()) { if (reader.NodeType != XmlNodeType.Element || reader.Name != "rc") continue; var attr = reader.GetAttribute("int_ESR"); if (!goodEsrValues.Contains(attr)) continue; var name = reader.GetAttribute("str_Name"); if (name != null) yield return name; } }