Formatting of XML created by DataContractSerializer
Solution 1
As bendewey says, XmlWriterSettings is what you need - e.g. something like
var ds = new DataContractSerializer(typeof(Foo));
var settings = new XmlWriterSettings { Indent = true };
using (var w = XmlWriter.Create("fooOutput.xml", settings))
ds.WriteObject(w, someFoos);
Solution 2
Take a look at the Indent
property of the XmlWriterSettings
Update: Here is a good link from MSDN on How to: Specify the Output format on the XmlWriter
Additionally, here is a sample:
class Program
{
static void Main(string[] args)
{
var Mark = new Person()
{
Name = "Mark",
Email = "[email protected]"
};
var serializer = new DataContractSerializer(typeof(Person));
var settings = new XmlWriterSettings()
{
Indent = true,
IndentChars = "\t"
};
using (var writer = XmlWriter.Create(Console.Out, settings))
{
serializer.WriteObject(writer, Mark);
}
Console.ReadLine();
}
}
public class Person
{
public string Name { get; set; }
public string Email { get; set; }
}
Solution 3
Be careful about adjusting whitespace in XML documents! Adjusting whitespace will make the XML more readable for us humans, but it may interfere with machine parsing.
According to the XML standard, whitespace is significant by default. In other words, as far as XML is concerned, white space is content.
If you feed your nicely formatted XML into an XML Document object, you will get a different result than the version that has no spaces or line breaks in it. You will get additional text nodes added to the version that has been formatted.
This MSDN article on XML White Space has several examples that show how tricky white space can be.
If you're formatting the XML only for human consumption, it doesn't matter. But if you try to round-trip your formatted document, you could run into trouble.
Since one of the key primary benefits of using DataContractSerializer is the ability to serialize objects and deserialize XML seamlessly, it's usually best to leave the ugly output alone.
I usually paste the output into NotePad++ and run an XML-tidy macro over it when I want to read it for debugging purposes.
Solution 4
public static string SerializeEntity<T>(T source)
{
using (MemoryStream ms = new MemoryStream())
{
NetDataContractSerializer serializer = new NetDataContractSerializer();
serializer.Serialize(ms, source);
return System.Text.Encoding.ASCII.GetString(ms.ToArray());
}
}
public static T DeSerializeEntity<T>(string xml)
{
using (MemoryStream ms = new MemoryStream(System.Text.Encoding.ASCII.GetBytes(xml)))
{
NetDataContractSerializer serializer = new NetDataContractSerializer();
return (T)serializer.Deserialize(ms);
}
}
Eric Anastas
Updated on February 23, 2020Comments
-
Eric Anastas about 4 years
Is there an easy way to get DataContractSerializer to spit out formatted XML rather then one long string? I don't want to change the tags or content in any way, just have it add line breaks and indentation to make the XML more readable?
<tagA> <tagB>This is</tagB> <tagC>Much</tagC> <tagD> <tagE>easier to read</tagE> </tagD> </tagA> <tagA><tagB>This is</tagB><tagC>Much</tagC><tagD><tagE>harder to read</tagE></tagD></tagA>
-
Jonathan Allen almost 14 yearsShouldn't that be UTF8, not ASCII?
-
Michael Freidgeim almost 12 yearsShortcut for NotePad++ an XML-tidy macro see stackoverflow.com/questions/8170740/…
-
escape-llc about 8 yearsWhite space occurring "outside" elements is not significant whitespace; it gets tricky depending on the content model (e.g. element vs mixed content), and for sure whitespace within an element or attribute is significant, so no indenting of multi-line element content! I find that
DataContractSerializer
has no problems deserializing "indented" documents of its own creation.