«

I've developed a control that itself generates child controls dynamically,
and everything works great, including capturing events from child controls,
child controls maintaining their own view state, etc.

My one problem is that any values I add to the ViewState dictionary (I'm
currently adding them in my Page_Load handler) do not survive the postback.
They simply disappear. My control derives from WebControl (which is a
requirement), and everything I can find leads me to believe I should be able
to use ViewState without additional code to save/load it.

As a test, I tried to manually mess with overriding SaveViewState and
LoadViewState. For some reason, the object passed to LoadViewState was always
null.

TIA,
Nathan

Nathan,
if you've overridden the viewstate handling at the control level, and come
up with a null viewstate collection, perhaps the viewstate is turned off at
the page/control level or the .config file level. if that's not the case,
make sure you're calling the base.SaveViewState() method of you're overriden
viewstate handler...

Mike

"Nathan Brady" <Nathan > wrote in message
news:31007FAF-A7A3-41FC-86C7-...
> I've developed a control that itself generates child controls dynamically,
> and everything works great, including capturing events from child
controls,
> child controls maintaining their own view state, etc.
>
> My one problem is that any values I add to the ViewState dictionary (I'm
> currently adding them in my Page_Load handler) do not survive the
postback.
> They simply disappear. My control derives from WebControl (which is a
> requirement), and everything I can find leads me to believe I should be
able
> to use ViewState without additional code to save/load it.
>
> As a test, I tried to manually mess with overriding SaveViewState and
> LoadViewState. For some reason, the object passed to LoadViewState was
always
> null.
>
> TIA,
> Nathan
>