Hi,
Robert Jordan wrote: > > On 02.02.2010 14:35, PFJ wrote: >>> Thus, the only *clean* way to solve this is introducing a shared >>> assembly implementing the classes you want to serialize. It's a >>> common pattern. >>> >> >> As the serializer is only used once, can the other app just deserialize >> and >> use it? I've reimplemented the Elements class but now just have a little >> problem in accessing it... > > It doesn't matter how often, in which way or how symmetric > the de/serialization is performed. What counts is the type identity. > Hmm, I guess that is why after I've sorted out the code (thanks), added in the Elements class and now have it compiled, I'm getting the same error as I did originally (SerializationError - can't find 'elements'). I'm running the debugger on the code that generates the binaryserialized form and when I look at the debug information (I admit, this is under VS2008) it says elementgo Count=111 with a plus icon before the element go. click on the + icon and it says + 0 {elements.Form1.Elements}. click on the + icon and it gives me the copy of the list. Is it this {elements.Form1.Elements} it's objecting to? TTFN Paul -- View this message in context: http://old.nabble.com/Problem-with-BinarySerialization-tp27419333p27433786.html Sent from the Mono - Dev mailing list archive at Nabble.com. _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list