G
Guest
Hi Tom,
This issue generally comes up due to conflicting namespaces. If you were to
check the binary stream in the file, you would notice that it contains the
class' namespace mentioned somewhere withing the binary code. Now when you
try to deserialise it in a different application, you need to deserialise the
stream into the same object. Thus the only point of concern lies in selecting
the right object to deserialise into.
I did face this problem sometime ago, and I did get around this by properly
managing the namespace of the final object.
Hope this helps,
Nick
This issue generally comes up due to conflicting namespaces. If you were to
check the binary stream in the file, you would notice that it contains the
class' namespace mentioned somewhere withing the binary code. Now when you
try to deserialise it in a different application, you need to deserialise the
stream into the same object. Thus the only point of concern lies in selecting
the right object to deserialise into.
I did face this problem sometime ago, and I did get around this by properly
managing the namespace of the final object.
Hope this helps,
Nick