"Rowland Shaw" <spamfilter@anotherpointless.org> wrote in message
news:416E3293-A203-40C8-9127-0A3B2D3BB0BE@microsoft.com...
> All the documentation I've found suggects that all you need to support on
> your object to stick it in the ViewState on a control is the IStateManager
> interface.
>
> However, with the IStateManager interface implemented (in my example on
> ComplexObject), I get the infamous error:
> [HttpException (0x80004005): The type 'MyCompany.MyProject.ComplexObject'
> must be marked as Serializable or have a TypeConverter other than
> ReferenceConverter to be put in viewstate.]
>
> There's been a lot of head scratching, and a lot of flicking through pages
> 245 to 255 of MS Press' "Developing Asp.Net Server Controls and
> Components";
> but I'm still no wiser -- am I missing something blindingly obvious or is
> there really an amount of black magic required? (I suspect the former)

"Rowland Shaw" <spamfilter@anotherpointless.org> wrote in message
news:416E3293-A203-40C8-9127-0A3B2D3BB0BE@microsoft.com...
> All the documentation I've found suggects that all you need to support on
> your object to stick it in the ViewState on a control is the IStateManager
> interface.
>
> However, with the IStateManager interface implemented (in my example on
> ComplexObject), I get the infamous error:
> [HttpException (0x80004005): The type 'MyCompany.MyProject.ComplexObject'
> must be marked as Serializable or have a TypeConverter other than
> ReferenceConverter to be put in viewstate.]
>
> There's been a lot of head scratching, and a lot of flicking through pages
> 245 to 255 of MS Press' "Developing Asp.Net Server Controls and
> Components";
> but I'm still no wiser -- am I missing something blindingly obvious or is
> there really an amount of black magic required? (I suspect the former)

"Teemu Keiski" wrote:

> And to add, yes option to having Serializable attribute is developing a
> TypeConverter for your object, it is the most efficient solution from
> viewstate standpoint. The key point in understanding what I said is
> explained on pages 245-246
>
> --
> Teemu Keiski
> ASP.NET MVP, AspInsider
> Finland, EU
>
>
> "Rowland Shaw" <spamfilter@anotherpointless.org> wrote in message
> news:416E3293-A203-40C8-9127-0A3B2D3BB0BE@microsoft.com...
> > All the documentation I've found suggects that all you need to support on
> > your object to stick it in the ViewState on a control is the IStateManager
> > interface.
> >
> > However, with the IStateManager interface implemented (in my example on
> > ComplexObject), I get the infamous error:
> > [HttpException (0x80004005): The type 'MyCompany.MyProject.ComplexObject'
> > must be marked as Serializable or have a TypeConverter other than
> > ReferenceConverter to be put in viewstate.]
> >
> > There's been a lot of head scratching, and a lot of flicking through pages
> > 245 to 255 of MS Press' "Developing Asp.Net Server Controls and
> > Components";
> > but I'm still no wiser -- am I missing something blindingly obvious or is
> > there really an amount of black magic required? (I suspect the former)
>
>