Dynamic controls

[Mike]

Hi,

I am building a web form with dynamic controls. Some need to be visible and some not. When clicking on a button, all controls become visible. I have used code behind to do that, but when I set the value of a control (ie. label) and then click the button to show all controls, these value are lost. Should I use ViewState and save the state of each single control? Or is that a better method? Any resouce or sample would be highly appreciated.

Thanks
Mike

[David Coe, MCAD]

The ViewState should intrinsically hold the set values, unless somewhere in the process (Page_Load, etc.) they are getting re-loaded with blank text.

"Mike" wrote:

Hi,

I am building a web form with dynamic controls. Some need to be visible and some not. When clicking on a button, all controls become visible. I have used code behind to do that, but when I set the value of a control (ie. label) and then click the button to show all controls, these value are lost. Should I use ViewState and save the state of each single control? Or is that a better method? Any resouce or sample would be highly appreciated.

Thanks
Mike

[Ken Cox [Microsoft MVP]]

You might want to check out Denis Bauer's free DynamicControlsPlaceholder
control that seems to do what you need:

It "behaves like a placeholder but additionally handles recreating dynamic
controls on subsequent requests."

http://www.denisbauer.com/ASPNETCont...aceholder.aspx

"Mike" <no****@nospam.com> wrote in message
news:%2***************@TK2MSFTNGP12.phx.gbl...

Hi,

I am building a web form with dynamic controls. Some need to be visible and
some not. When clicking on a button, all controls become visible. I have
used code behind to do that, but when I set the value of a control (ie.
label) and then click the button to show all controls, these value are lost.
Should I use ViewState and save the state of each single control? Or is that
a better method? Any resouce or sample would be highly appreciated.

Thanks
Mike

[Saravana [MVP]]

Check out this article to know how to maintain viewstate in dynamically created controls,
http://www.codeproject.com/aspnet/retainingstate.asp

--
Saravana
Microsoft MVP - ASP.NET
www.extremeexperts.com

"Mike" <no****@nospam.com> wrote in message news:#s*************@TK2MSFTNGP12.phx.gbl...

Hi,

I am building a web form with dynamic controls. Some need to be visible and some not. When clicking on a button, all controls become visible. I have used code behind to do that, but when I set the value of a control (ie. label) and then click the button to show all controls, these value are lost. Should I use ViewState and save the state of each single control? Or is that a better method? Any resouce or sample would be highly appreciated.

Thanks
Mike

[Ibrahim Shameeque]

Mike
You have to be careful when setting the value, because the button click event happens after the pageload event and as David says the value might be set to blank on page load.
--
Ibrahim

"David Coe, MCAD" wrote:

The ViewState should intrinsically hold the set values, unless somewhere in the process (Page_Load, etc.) they are getting re-loaded with blank text.

"Mike" wrote:

Hi,

I am building a web form with dynamic controls. Some need to be visible and some not. When clicking on a button, all controls become visible. I have used code behind to do that, but when I set the value of a control (ie. label) and then click the button to show all controls, these value are lost. Should I use ViewState and save the state of each single control? Or is that a better method? Any resouce or sample would be highly appreciated.

Thanks
Mike