W
WhoopDing
Why does my viewstate not seem to have an effect after the first server
roundtrip?
roundtrip?
P
Pete Wright
because you are not rebuilding it probably.
Viewstate is not automatically persistent across server round trips - it
needs to be generated on each trip to the server.
Viewstate is not automatically persistent across server round trips - it
needs to be generated on each trip to the server.
P
Pete Wright
This is what happens when I post newsgroup messages first thing in the
morning, but do I ever learn my lesson??
I was confused.
An aspx is called, viewstate is populated and the page is rendered. When a
postback occurs viewstate is there to be used, and will remain there until
you redirect off the page to a different URL. However, the confusion on my
part is that viewstate will get "lost" or corrupted if during the postback
an object is hyrdated from the viewstate and changed. That object needs to
be put back into viewstate since viewstate is not a reference to a live
object.
My apologies for that
morning, but do I ever learn my lesson??
I was confused.
An aspx is called, viewstate is populated and the page is rendered. When a
postback occurs viewstate is there to be used, and will remain there until
you redirect off the page to a different URL. However, the confusion on my
part is that viewstate will get "lost" or corrupted if during the postback
an object is hyrdated from the viewstate and changed. That object needs to
be put back into viewstate since viewstate is not a reference to a live
object.
My apologies for that
P
Pete Wright
This is what happens when I post newsgroup messages first thing in the
morning, but do I ever learn my lesson??
I was confused.
An aspx is called, viewstate is populated and the page is rendered.
When a postback occurs viewstate is there to be used, and will remain
there until you redirect off the page to a different URL. However, the
confusion on my part is that viewstate will get "lost" or corrupted if
during the postback an object is hyrdated from the viewstate and
changed. That object needs to be put back into viewstate since
viewstate is not a reference to a live object.
My apologies for that
morning, but do I ever learn my lesson??
I was confused.
An aspx is called, viewstate is populated and the page is rendered.
When a postback occurs viewstate is there to be used, and will remain
there until you redirect off the page to a different URL. However, the
confusion on my part is that viewstate will get "lost" or corrupted if
during the postback an object is hyrdated from the viewstate and
changed. That object needs to be put back into viewstate since
viewstate is not a reference to a live object.
My apologies for that