Click here to Skip to main content
Click here to Skip to main content

ViewState management for dynamically loaded UserControls

, 30 Apr 2007 CPOL
Rate this:
Please Sign up or sign in to vote.
ViewState management for dynamically loaded UserControls.


In many of our business ASPX applications, there is a need for special UserControls that perform specific functionalities so that they can be easily re-used in the entire application. There are two ways we can use a UserControl: either we drag it onto the form, or we load it dynamically through the use of LoadControl("MyUserControl.ascx"). When we use the second method, we (all?) encounter one major problem: ViewState persistence! Upon postback, when we re-load the control in our CS code, .NET Framework forgets everything about its previous state. This tiny essay addresses this issue.


Straightforward: assign the dynamically loaded control the same ID it had just before the data postback! In fact, .NET Framework retains the state of every user control (even of those dynamically loaded) and associate them with their programmatic IDs; after a postback, it tries to find the same controls with the same IDs in order to load their previous state. The whole thing can better be explained through an example Smile | :)


We'll create a simple UserControl which has a TexBox, we'll also have an ASPX form on which we use this control but in three ways. For this purpose, we'll create three instances:

  • An instance which is already dragged onto the form
  • An instance dynamically created through LoadControl()
  • An instance dynamically created through LoadControl() with its ID preserved

I have created a simple UserControlViewStateManager that will help us automatically save/load the dynamically loaded controls and their IDs. The main idea behind this gadget is to save the ID of the UserControls right after loading them into their parent container and re-creating them after the postback: the best place for re-creating the controls is the Page_Init event.

When creating a new user control: just give a unique ID and at the same time, add it to an instance of the UserControlViewStateManager. Shown below is a snippet:

Control userControl = LoadControl("MyUserControl.ascx");
userControl.ID = (placeHolder2.Controls.Count - 1).ToString();

In the Page_Init event, call ReCreateControlsID() of the helper class, passing it the container object as a parameter:

ucViewStateManager = new UserControlViewStateManager("SomeUniqueSessionID");

Hope this helps Smile | :) In the demo application, you can find the entire source code.


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Wesam Elsawirki
Software Developer (Senior)
Hungary Hungary
Professional Software Developer, currently working for HVB bank.
Programming experience includes: C#, ASP.NET, Delphi, PHP, VB.
Technologies: MS SQL Server 2005, Apache, IIS.
Certifications: MCAD, MCSD, MCTS (MS SQL Server 2005), MCITP

Comments and Discussions

GeneralMessage Automatically Removed PinmemberAytha24-Nov-11 2:10 
GeneralMore about Dinamically added controls Pinmemberrafael.aca14-Apr-09 13:06 
GeneralDynamice Usercontrol .ascx PinmemberKurmala13-Jul-08 20:50 
GeneralUser Controls Piling UP on Page [modified] Pinmemberstanz927-Feb-08 8:04 
GeneralIs this a sure tested method of loading usercontrols dynamically Pinmemberxsoftdev19-Feb-08 14:12 
GeneralPass values to other user controls Pinmemberxsoftdev18-Oct-07 16:55 
GeneralRe: Pass values to other user controls PinmemberWesam E.20-Oct-07 4:56 
GeneralRe: Pass values to other user controls Pinmemberxsoftdev26-Nov-07 7:52 
GeneralLoad one and Unload the others Pinmemberxsoftdev4-Oct-07 10:00 
GeneralRe: Load one and Unload the others PinmemberWesam E.8-Oct-07 21:04 
GeneralUserControl PinmemberBrother Louis20-Aug-07 1:54 
GeneralRe: UserControl PinmemberWesam E.8-Oct-07 20:59 
Questionquestion from manish.2004 PinadminSean Ewington1-Jun-07 10:04 
AnswerRe: question from manish.2004 PinmemberWesam E.4-Oct-07 21:23 
GeneralRe: question from manish.2004 Pinmemberxsoftdev22-Nov-07 1:50 
QuestionIssues at Page PostBack Pinmembermkhiami27-Apr-07 11:40 
QuestionThread-Safe ??? PinmemberMarco M.18-Apr-07 10:06 
AnswerRe: Thread-Safe ??? PinmemberJohnno7423-Apr-07 17:57 
GeneralRe: Thread-Safe ??? PinmemberWesam E.30-Apr-07 1:08 
GeneralRe: Thread-Safe ??? PinmemberJohnno7430-Apr-07 13:50 
GeneralControl issue PinmemberVolleyknaller17-Apr-07 23:39 
GeneralRe: Control issue PinmemberWesam E.18-Apr-07 1:35 
GeneralRe: Control issue PinmemberVolleyknaller18-Apr-07 2:18 
QuestionPostback issue Pinmemberinetfly12317-Apr-07 12:01 
AnswerRe: Postback issue PinmemberWesam E.17-Apr-07 20:59 
Yes, indeed. I had a similar problem and I had solved it this way. As I mentioned, the basic idea behind all this is to re-create the UserControls alongside their ID's (to make the available to Framework just as they were before the postback).
.Net Framework saves the viewstate of every Server control (including UserControls), so they are not lost! Upon data postback it will try to find those controls again by their ID's: if it finds them, it will reload the value otherwise nothing happens Cool | :cool:
The helper class I made will take care of all all this - all what you need to do is add the control to helper class when you create it (the helper class) and one line in Page_Init which will re-create all controls already added. Hope this helps!

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web03 | 2.8.150302.1 | Last Updated 30 Apr 2007
Article Copyright 2007 by Wesam Elsawirki
Everything else Copyright © CodeProject, 1999-2015
Layout: fixed | fluid