Applied XML Programming for Microsoft .NET.pdf - Csbdu.in

}sw.Write(sb.ToString());sw.Close();The output is shown in Figure 4-1. Apparently, everything is working just fine.Figure 4-1: The sample XML file is successfully recognized and managed by MicrosoftInternet Explorer.One small drawback is that the XML code you get is not exactly in the format youexpect—the format shown in Internet Explorer. The source code for the XML file inFigure 4-1 has no newline characters or indentation and appears to be an endless andhardly readable string of markup text. But this is no big deal. You can simply enhancethe code a little bit by adding newline and tab characters.In general, there is nothing really bad or wrong with this approach as long as thedocument file you need to create is simple, has minimal structure, and has only a fewlevels of nesting. When you have more advanced and stricter requirements such asprocessing instructions, namespaces, indentation, formatting, and entities, thecomplexity of your code can grow exponentially and, with it, the likelihood of introducingerrors and bugs.Let's rewrite our sample file using .NET XML writers, as shown in the following code. A.NET XML writer features ad hoc write methods for each possible XML node type andmakes the creation of XML output more logical and much less dependent on theintricacies, and even the quirkiness, of the markup languages.void CreateXmlFileUsingWriters(String[] theArray,string filename){// Open the XML writer (default encoding charset)XmlTextWriter xmlw = new XmlTextWriter(filename, null);xmlw.Formatting = Formatting.Indented;xmlw.WriteStartDocument();xmlw.WriteStartElement("array");foreach(string s in theArray)112