SelectedItem null after either code rebuild or app pool recycle

[James Daresta]

I have an issue with the combo boxes when either the app pool is recycled or a new build is deployed. If a user is on a page with a combobox and while working on it back at the server the app pool recycles or a new build is deployed when they then post back to the server the SelectedItem is null in the server code. The Text property still has its value however. I have spent a large amount of time trying to figure out why it does this. So my question is this by design? Does the combobox use either session or such behind the scenes and when the app recycles it is lost?

I am not posting code, but if you take a page with a combox box, a button and put it in a IIS web site you can then reproduce it. Simply got to the page and while on it recycle the app pool and then submit the form. Try then to access the selected item and you will see its null while the Text has a value.

Short of never doing recycles I am not sure what to do to prevent this. Thanks.

[James Daresta]

Please disregard. I find the issue. RadSessionPageStateCompression had been implemented and since the recycling was killing the sessions this caused the issue. Sorry for the trouble.