Predefine XML namespaces for DataContractSerializer
static void Main()
{
var o = new Foo {
Prop = new Dictionary<string,string> { {"foo","bar"} }
};
var ms = new MemoryStream();
var slz = new DataContractSerializer(typeof(Foo));
slz.WriteObject(ms, o,
new Dictionary<string,string>
{
{ "arr", "http://schemas.microsoft.com/2003/10/Serialization/Arrays" },
});
string data = Encoding.UTF8.GetString(ms.ToArray());
Console.WriteLine(data);
}
public static class Extensions
{
public static void WriteObject(
this DataContractSerializer serializer,
Stream stream, object data,
Dictionary<string,string> namespaces)
{
using (var writer = XmlWriter.Create(stream))
{
serializer.WriteStartObject(writer, data);
foreach (var pair in namespaces)
{
writer.WriteAttributeString("xmlns", pair.Key, null, pair.Value);
}
serializer.WriteObjectContent(writer, data);
serializer.WriteEndObject(writer);
}
}
}
[DataContract]
class Foo
{
[DataMember]
public Dictionary<string,string> Prop;
}
Output:
<?xml version="1.0" encoding="utf-8"?>
<Foo xmlns:arr="http://schemas.microsoft.com/2003/10/Serialization/Arrays"
xmlns:i="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://schemas.datacontract.org/2004/07/">
<Prop>
<arr:KeyValueOfstringstring>
<arr:Key>foo</arr:Key>
<arr:Value>bar</arr:Value>
</arr:KeyValueOfstringstring>
</Prop>
</Foo>
I successfully used the solution described here: http://blogs.msdn.com/b/youssefm/archive/2009/07/24/optimizing-away-repeat-xml-namespace-declarations-with-datacontractserializer.aspx
You basically create a behavior which adds the namespaces to the root element for you.
From the article:
Just create a serializer that inherits from XmlObjectSerializer that uses a DataContractSerializer for all of its methods, except for the fact that it registers additional namespaces at the top level. Then create a behavior that derives from
DataContractSerializerOperationBehavior
with aCreateSerializer
method that returns theXmlObjectSerializer
you just created and plug in the behavior.
In case you want to do it in Silverlight, you can also use the solution described here: http://blogs.msdn.com/b/carlosfigueira/archive/2011/05/24/wcf-extensibility-custom-serialization-in-silverlight.aspx