<ChristophDotNet

# re: Improvements to the XmlSerializer in Whidbey

"The new imperative model for the XmlSerializer opens up the previously unsupported interface IXmlSerializable."
FINALLY!

At last we can reroute our ToXml() methods to a method that is understood by XmlSerializer so it can serialize our classes which are build with interfaces (because they have to be generic) and interfaces are a concept the XmlSerializer has never heard of...

# re: Improvements to the XmlSerializer in Whidbey

I don't see a fix for serialization of objects that have interface properties. I can't see how anyone is using the XMLSerializer with this limitation.

# re: Improvements to the XmlSerializer in Whidbey

Andrew,

Serialization of interface properties is probably not a priority because it doesn't map to anything in the XSD type system.

There are also questions about how to embed enough type information about the interface in the serialized output in a schema valid way. Without that information how would you be able to deserialize it back?

It boils down to the fact that the XmlSerializer is not intended to flatten object graphs for persistent storage. It to translate between strongly typed XML documents and runtime objects.

Christoph

# re: Improvements to the XmlSerializer in Whidbey

We frequently serialize with interface objects. It requires you to create two sets of methods.. for example

public class MyClass : IMyClass
{
private MyObject m_oObject;

public MyObject OneToWriteToXml
{
get { return this.m_oObject; }
set { this.m_oObject=value; }
}


IMyObject IMyClass.OneToWriteToXml
{
get { return this.OneToWriteToXml; }
set { this.OneToWriteToXml=(MyObject)value }
}
}

My Interface methods simply 'thunk' to the classes public method. This allows you to use an interface as well as serialize.

If you need to serialize objects that are derived from other objects, I generally create an abstract base class, and make all the objects derived from it that I will be returning. As long as you have the objects listed in the XmlSerializers array, they appear to deserialize fine.


I think they should update the XmlSerializer/DeSerializer to handle the case where protected/private data is attributed with XmlAttribute/XmlElement to be put into the Serialized Xml as well.

John

# re: Santa (e.g. Bill G). For Christmas can I get control of the xml serialization process?

# re: If I don't understand it, or it doesn't work the way I expect it to then it is broken

As far as IXmlSerializable goes, in framework 1.0 and 1.1 it bears the following description:

# re: Improvements to the XmlSerializer in Whidbey

<a href= http://index1.elurker.com >combining ceramics fused glass</a>

# re: Improvements to the XmlSerializer in Whidbey

<a href= spiritez.com ></a>