By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,641 Members | 1,446 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,641 IT Pros & Developers. It's quick & easy.

Serialization woes

P: n/a
Hello,

I've been battling over this problem for
the better part of a day, so I'd appreciate it
if someone could shed some light here.

I have a file which is produced by the custom binary
serialization of an object (i.e. by implementing the
ISerializable interface). This object has a hashtable
as one of its members, and this hashtable is
properly populated before the object that
contains it is serialized to disk (again using
custom serialization).

I can confirm that when the file is created, it
has information on the contents of the hashtable.

However, when the object is deserialized, the
hashtable now has all the data zapped from it.

I've checked and rechecked that I am using the
right names to put data in the SerializationInfo
object in GetObjectData, and to extract the data
in the special serialization constructor.

I wish I could know what went on behind
the scenes between the call to deserialize the
object and the call to the special constructor.
It's as if the SerializationInfo object is not
being properly populated from the data in the
file.

Any help would be greatly appreciated.

--
Akin

aknak at aksoto dot idps dot co dot uk
Nov 21 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Have you looked and compared your code to the
System.Runtime.Serialization.ISerializable overview in the help file ?

--

OHM ( Terry Burns )
. . . One-Handed-Man . . .
If U Need My Email ,Ask Me

Time flies when you don't know what you're doing

"Wild Wind" <no****@blackhole.com> wrote in message
news:2o************@uni-berlin.de...
Hello,

I've been battling over this problem for
the better part of a day, so I'd appreciate it
if someone could shed some light here.

I have a file which is produced by the custom binary
serialization of an object (i.e. by implementing the
ISerializable interface). This object has a hashtable
as one of its members, and this hashtable is
properly populated before the object that
contains it is serialized to disk (again using
custom serialization).

I can confirm that when the file is created, it
has information on the contents of the hashtable.

However, when the object is deserialized, the
hashtable now has all the data zapped from it.

I've checked and rechecked that I am using the
right names to put data in the SerializationInfo
object in GetObjectData, and to extract the data
in the special serialization constructor.

I wish I could know what went on behind
the scenes between the call to deserialize the
object and the call to the special constructor.
It's as if the SerializationInfo object is not
being properly populated from the data in the
file.

Any help would be greatly appreciated.

--
Akin

aknak at aksoto dot idps dot co dot uk

Nov 21 '05 #2

P: n/a

"Wild Wind" <no****@blackhole.com> wrote in message
news:2o************@uni-berlin.de...
Hello,

I've been battling over this problem for
the better part of a day, so I'd appreciate it
if someone could shed some light here.

I have a file which is produced by the custom binary
serialization of an object (i.e. by implementing the
ISerializable interface). This object has a hashtable
as one of its members, and this hashtable is
properly populated before the object that
contains it is serialized to disk (again using
custom serialization).

I can confirm that when the file is created, it
has information on the contents of the hashtable.

However, when the object is deserialized, the
hashtable now has all the data zapped from it.

I've checked and rechecked that I am using the
right names to put data in the SerializationInfo
object in GetObjectData, and to extract the data
in the special serialization constructor.

I wish I could know what went on behind
the scenes between the call to deserialize the
object and the call to the special constructor.
It's as if the SerializationInfo object is not
being properly populated from the data in the
file.


OK, it seems from googling around that the problem
is caused by the hashtable not being populated with
its elements *until* deserialization is complete -
at the time I am still deserializing it in the
special deserialization constructor, this hasn't
happened so there are no items in it.

It also turns out that the solution is for the class
that contains the hashtable and is being serialized/
deserialized to implement the IDeserializationCallback
interface and access the hashtable in the OnDeserialization
method of that call.

--
Akin

aknak at aksoto dot idps dot co dot uk
Nov 21 '05 #3

P: n/a
Hi,
I ran into the same problem. However in the OnDeserialization
the hashTable member is still empty. it is only populated after the stream is closed.
Were you able to find a solution to this?

Thanks,
Koichiro
Hello,

I've been battling over this problem for
the better part of a day, so I'd appreciate it
if someone could shed some light here.

I have a file which is produced by the custom binary
serialization of an object (i.e. by implementing the
ISerializable interface). This object has a hashtable
as one of its members, and this hashtable is
properly populated before the object that
contains it is serialized to disk (again using
custom serialization).

I can confirm that when the file is created, it
has information on the contents of the hashtable.

However, when the object is deserialized, the
hashtable now has all the data zapped from it.

I've checked and rechecked that I am using the
right names to put data in the SerializationInfo
object in GetObjectData, and to extract the data
in the special serialization constructor.

I wish I could know what went on behind
the scenes between the call to deserialize the
object and the call to the special constructor.
It's as if the SerializationInfo object is not
being properly populated from the data in the
file.

Any help would be greatly appreciated.

--
Akin

aknak at aksoto dot idps dot co dot uk


User submitted from AEWNET (http://www.aewnet.com/)
Nov 21 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.