Why does viewstate deserialize object as hashtable?

[jw56578]

I have an object that inherits from hashtable and is serializable to be
stored in the viewstate, but when I retrieve it from viewstate, it is
converted into a hashtable, why won't it stay as the original object?
thanks

[Teemu Keiski]

Hi,

Your question is confusing. Define what means "it is converted into
HashTable" (post the code). Do you mean that you are handed with Hashtable
instance even though it is derived from HT (did you do casting to the
derived type after getting object from the Viewstate and got exceptions)?

I'd like to see the sample code. And you did specify serialization by
appending Serializable attribute or did you reimplement ISerializable
inetrface implemented by HT?

One reason I'm thinking for this, is that Hashtable implements ISerializable
interface, and I suppose it could be possible that its default
implementation is used (which would instantiate Hashtable), unless you
redeclare it. (though it sounds weird)

--
Teemu Keiski
ASP.NET MVP, AspInsider
Finland, EU

<jw*****@gmail.com> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...

I have an object that inherits from hashtable and is serializable to be
stored in the viewstate, but when I retrieve it from viewstate, it is
converted into a hashtable, why won't it stay as the original object?
thanks

[PJ]

> One reason I'm thinking for this, is that Hashtable implements
ISerializable

interface, and I suppose it could be possible that its default
implementation is used (which would instantiate Hashtable), unless you
redeclare it. (though it sounds weird)

That's exactly right. Asp.net calls the ISerializable methods and since you
do not override the appropriate methods in your derived object, it uses the
hashtables implementation...which, of course, only serializes and
deserializes itself.

[jw56578]

when i say converts it to a hashtable, i mean that the type of the
deserialized object is Hashtable, not my original object.