I eventually figured out there was a byte mark exception and removed it using this code: string _byteOrderMarkUtf8 = Encoding.UTF8.GetString(Encoding.UTF8.GetPreamble()); if (xml.StartsWith(_byteOrderMarkUtf8)) { var lastIndexOfUtf8 = _byteOrderMarkUtf8.Length-1; xml = xml.Remove(0, lastIndexOfUtf8); }
No, you check it by looking at XmlReader.IsEmptyElement. In the docs for that property: A corresponding EndElement node is not generated for empty elements.
Look at this. In short, you need to change OfConcreteType<Service1>() to ConstructedBy(() => new Service1());.
The reality of your file’s encoding appears to conflict with that specified by your XML declaration. If your file actually uses one-byte characters, declaring encoding=”utf-16″ won’t change it to use two-byte characters, for example. Try removing the conflicting encoding from the XML declaration. Replace <?xml version=”1.0″ encoding=”utf-16″?> with <?xml version=”1.0″?> You may also be able … Read more
First, some background. What is a DTD? The document you are trying to parse contains a document type declaration; if you look at the document, you will find near the beginning a sequence of characters beginning with <!DOCTYPE and ending with the corresponding >. Such a declaration allows an XML processor to validate the document … Read more
Use XmlReader to parse large XML documents. XmlReader provides fast, forward-only, non-cached access to XML data. (Forward-only means you can read the XML file from beginning to end but cannot move backwards in the file.) XmlReader uses small amounts of memory, and is equivalent to using a simple SAX reader. using (XmlReader myReader = XmlReader.Create(@”c:\data\coords.xml”)) … Read more
I’ve generally looked at it not from a fastest perspective, but rather from a memory utilization perspective. All of the implementations have been fast enough for the usage scenarios I’ve used them in (typical enterprise integration). However, where I’ve fallen down, and sometimes spectacularly, is not taking into account the general size of the XML … Read more
It all depends on how big the unit of work, but I guess you’re trying to treat each <product/> nodes in succession. For that, the simplest way would be to use XMLReader to get to each node, then use SimpleXML to access them. This way, you keep the memory usage low because you’re treating one … Read more
My experience of XmlReader is that it’s very easy to accidentally read too much. I know you’ve said you want to read it as quickly as possible, but have you tried using a DOM model instead? I’ve found that LINQ to XML makes XML work much much easier. If your document is particularly huge, you … Read more