Form controls and code behind

[Roshawn Dawson]

Hi,

Suppose I have an form that contains any number of controls. To access
these controls programatically and get/set the state of their
properties, must they all be server controls (have the runat="server"
attribute)?

Thanks,
Roshawn

[Eliyahu Goldin]

Roshawn,

If you mean server-side access, then yes. You can always access any controls
on client side.

Eliyahu

"Roshawn Dawson" <ud****@bellsouth.net> wrote in message
news:%2****************@TK2MSFTNGP14.phx.gbl...

Hi,

Suppose I have an form that contains any number of controls. To access
these controls programatically and get/set the state of their
properties, must they all be server controls (have the runat="server"
attribute)?

Thanks,
Roshawn

[luminousc]

As long as the control is marked as runat="server" and has an ID it
should be accessible in the code behind as long as you define it inside
the main class.

[Steve C. Orr [MVP, MCSD]]

This applies to the HTML controls in the HTML tab of your VS.NET toolbox:
If you want to access the controls from your server side code then yes, they
will need the runat="server" attribute.
If you don't need to interact with the controls at all, or if you only want
to interact with the controls with client side script, then you don't need
the runat="server" attribute on the control and it's best for performance
reasons to leave it off.

Here's more info:
http://SteveOrr.net/faq/3in1.aspx#ServerControl

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://SteveOrr.net
"Roshawn Dawson" <ud****@bellsouth.net> wrote in message
news:%2****************@TK2MSFTNGP14.phx.gbl...

Hi,

Suppose I have an form that contains any number of controls. To access
these controls programatically and get/set the state of their properties,
must they all be server controls (have the runat="server" attribute)?

Thanks,
Roshawn