Technical ViewState question

[trepac-news7385]

Looong story, but here's the summary:

I'm dynamically generating a single TextBox control (always with the
same exact ID), but in a different location each time (there will be a
varying number of dynamically generated Labels before and after it).

As near as I can tell, when the control doesn't move it participates in
ViewState and it's data value persists between postbacks.

However, if it moves (there are more/fewer Labels before it than last
trip), it's data does not persist.

This surprises me. Although I don't understand ViewState on a deep
level, I thought data was persisted by the control's ID, not it's
relative position in the list of controls.
My questions:

Is ViewState data persisted by relative position, or by ID, or by some
other method?

Is it dangerous to be "moving" controls around like I am?

Is there a way to keep the data persistent (using ViewState) when the
control moves to a different location?
Thanks in advance for any help!

--Larry

[Scott Allen [MVP]]

Hi Larry:

Yes, the relative position of a control will change where the control's data
appears in the ViewState. There is good coverage of the topic here:

Understanding ASP.NET View State
http://msdn.microsoft.com/library/de.../viewstate.asp

--
Scott
http://www.OdeToCode.com/blogs/scott/

Looong story, but here's the summary:

I'm dynamically generating a single TextBox control (always with the
same exact ID), but in a different location each time (there will be a
varying number of dynamically generated Labels before and after it).

As near as I can tell, when the control doesn't move it participates
in ViewState and it's data value persists between postbacks.

However, if it moves (there are more/fewer Labels before it than last
trip), it's data does not persist.

This surprises me. Although I don't understand ViewState on a deep
level, I thought data was persisted by the control's ID, not it's
relative position in the list of controls.

My questions:

Is ViewState data persisted by relative position, or by ID, or by some
other method?

Is it dangerous to be "moving" controls around like I am?

Is there a way to keep the data persistent (using ViewState) when the
control moves to a different location?
Thanks in advance for any help!
--Larry

[trepac-news7385]

What a goldmine! Thanks a million, Scott.

--Larry