Saving a Collection to ViewState

[Angel]

I built a webcontrol and within the control I build a collection of properties I would Like to store so I do not have to rebuild it everytime there is a postback. I store the collection in viewstate and get the following error when I run a page with my control on it:

The Type 'myCollection' must be marked as Serializable or have a TypeConverter other than ReferenceConverter to be put in viewstate.

I store all my other custom properties in viewstate, but accessing myCollection from the viewstate becomes an error. I know that myCollection is not a basic type, while the other properties are, but is there a way to save the collection without having to rebuild it everytime there is a postback?

Thanks...

 

[Natty Gur]

Hi,

you need to mark your collection or derived classes, if exist, with
Serialization attribute.

Natty Gur[MVP]

blog : http://weblogs.asp.net/ngur
Mobile: +972-(0)52-8888377


*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!

 

[Angel]

Before the Class that I use into a collection I marked it with <Serializable()> and it still does not work...

Any ideas why not?

Thanks

 

[Andy Z Smith]

I think you will need to implement some custom serializers. The framework does not know to to serialize every possible class type that you can create. I've not done this but I think that's what it is.

My suggestion is to throw the stuff into something that is natively serializable. Add the salient parts of the collection to an ArrayList or a DataTable or something and shove it ViewState or Session.

Andrew

 

[Victor Garcia Aprea [MVP]]

Take a look at this[1] post to learn how the viewstate serializer works and
what you can do in order to get your data serialized fast and with the
smallest possible footprint.

[1]
http://weblogs.asp.net/vga/archive/2004/05/11/DontLetTheBinaryFormatterGetAtIt.aspx

--
Victor Garcia Aprea
Microsoft MVP | ASP.NET
Looking for insights on ASP.NET? Read my blog:
http://obies.com/vga/blog.aspx

I think you will need to implement some custom serializers. The framework

does not know to to serialize every possible class type that you can create.
I've not done this but I think that's what it is.

My suggestion is to throw the stuff into something that is natively

serializable. Add the salient parts of the collection to an ArrayList or a
DataTable or something and shove it ViewState or Session.