Page Adapters and View State
In saving view state, the page generates a string that represents the portion of view state that must be sent to the client. This string is an encoding of data that includes any private view state, and an identifier for any application view state saved in the session. With ASP.NET mobile controls, the page adapter must persist this string to the client and ensure that it is available on a subsequent postback.
On rendering, the page adapter must access the string through the page's ClientViewState property and write it out to the client.
On postback, the page adapter ensures that the persisted state is available in the form data by using the key defined by the ViewStateID static member of the MobilePage object (a string constant that is defined as "__VIEWSTATE").
Note Typically, you can have a page adapter write out this string as a hidden form variable whose name is the string specified by the ViewStateID field. When the form is submitted to the server as part of a postback, the value is automatically available in the form data, and the page adapter does not need to do any additional postback processing.