R – Postback problem for the custom control load wizard

This does create the new controls based on the incremented value, but all the control state is lost.

You're calling the function too late in the page life cycle. State is applied to your controls for the "Load" stage, and so if the controls are not created before that stage the state won't be restored, because the controls don't exist when it tries to apply the state.

You need to create the controls in the Page's Init event.

Personally, I'm not a fan of dynamic controls in ASP.Net. They have their place, but more often I choose a suitable maximum number of allowed controls, put them all on the page initially, and only enable/disable/hide/show them as needed.

It's hard to say much without seeing your code. However, a few things that might help:

1. You might want to look at the HTTP exchange during the failure using a web debugger like Fiddler; there's a good chance the answer will jump out at you.
2. Remember that F5 re-issues the last request. If you're navigating from one page to another, there shouldn't be any ViewState at all, unless you're doing a cross-page post.
3. If ViewState isn't being sent with the request, then perhaps the nature of the failure has something to do with the way you're encoding it?
4. LoadViewState() should only be called when the incoming request contains ViewState that needs to be loaded into the associated control.
5. SaveViewState() is called for every page request, to persist the control's state in a hidden field on the page, so that it's available during a postback.