I'm having a problem with my RadAjaxPanel and my viewstate.
We are keeping our last ten viewstates in session. The problem is on a certain page.. the user hits the page and selects a CATEGORY from a drop down. Another drop down is populated with CategoryTYPES depending on the CATEGORY that was selected.
To keep the page from posting back, I have a RadAjax panel around the controls on the page.
After selecting a CATEGORY/TYPE, the user can add that combination to a listbox and select another CATEGORY/TYPE. These selections are then used in a search that populates a RadGrid.
Our legacy system allowed the users to then use the browser back / forward buttons to move backward and forward, which loaded each viewstate version from memory. So each step was saved.
With my RadAjax panel on the page though, the hidden __VIEWSTATE value is not being updated on the page. I can see my SavePageStateToPersistenceMedium Sub is firing and that my subsequent viewstates are being saved to memory, but since the hidden field isn't being updated on the page, I'm continually loading the wrong version of the page (the original version from when I first hit the page) after doing an actual postback.
I think my main problem is the hidden field __VIEWSTATE is not getting updated. The hidden field has no runat="server" on it since it's being put there dynamically, and although I've managed to find the control and read the value from it, I can't find a way to update it during the ajax postback.
I've tried adding EnableViewState="true" to my ajax panel, but I'm still not updating the hidden field on the page when then ajax postback occurs.
I know I can't be the only one who's run into this and I'm hoping someone has a solution or even a work around that will allow me to keep track of where I'm at and what viewstate version I'm supposed to be loading when the user tries to browse backwards or forwards.
And yes, I know.. but they insist on being able to use the BACK and FORWARD browser buttons, so I have to live with it. :)
I appreciate any suggestions or tips on how I can get around this problem...
~TFlick
We are keeping our last ten viewstates in session. The problem is on a certain page.. the user hits the page and selects a CATEGORY from a drop down. Another drop down is populated with CategoryTYPES depending on the CATEGORY that was selected.
To keep the page from posting back, I have a RadAjax panel around the controls on the page.
After selecting a CATEGORY/TYPE, the user can add that combination to a listbox and select another CATEGORY/TYPE. These selections are then used in a search that populates a RadGrid.
Our legacy system allowed the users to then use the browser back / forward buttons to move backward and forward, which loaded each viewstate version from memory. So each step was saved.
With my RadAjax panel on the page though, the hidden __VIEWSTATE value is not being updated on the page. I can see my SavePageStateToPersistenceMedium Sub is firing and that my subsequent viewstates are being saved to memory, but since the hidden field isn't being updated on the page, I'm continually loading the wrong version of the page (the original version from when I first hit the page) after doing an actual postback.
I think my main problem is the hidden field __VIEWSTATE is not getting updated. The hidden field has no runat="server" on it since it's being put there dynamically, and although I've managed to find the control and read the value from it, I can't find a way to update it during the ajax postback.
I've tried adding EnableViewState="true" to my ajax panel, but I'm still not updating the hidden field on the page when then ajax postback occurs.
I know I can't be the only one who's run into this and I'm hoping someone has a solution or even a work around that will allow me to keep track of where I'm at and what viewstate version I'm supposed to be loading when the user tries to browse backwards or forwards.
And yes, I know.. but they insist on being able to use the BACK and FORWARD browser buttons, so I have to live with it. :)
I appreciate any suggestions or tips on how I can get around this problem...
~TFlick