Working with Server Controls
Declaring Server Controls Manipulating Server Controls Handling Control Action Events Handling Multiple Control Action Events Performing Page Navigation (Scenario 1) Performing Page Navigation (Scenario 2)
This section of the QuickStart illustrates some common core concepts and common actions performed by end users when using ASP.NET server controls within a page.
Declaring Server Controls
ASP.NET server controls are identified within a page using declarative tags that contain a runat="server" attribute. The following example declares three <asp:label runat="server"> server controls and customizes the text and style properties of each one individually.
You can programmatically identify an individual ASP.NET server control
within a page by providing it with an id attribute. You
can use this id reference to programmatically manipulate the server control's
object model at run time. For example, the following sample demonstrates how a page
developer could programmatically set an <asp:label runat="server"> control's
Text property within the Page_Load event.
ASP.NET server controls can optionally expose and raise server events, which
can be handled by page developers. A page developer may accomplish this
by declaratively wiring an event to a control (where the attribute
name of an event wireup indicates the event name and the attribute value
indicates the name of a method to call). For example, the following code
example demonstrates how to wire an OnClick event to a button control.
Event handlers provide a clean way for page developers to structure logic
within an ASP.NET page. For example, the following sample demonstrates how to
wire and handle four button events on a single page.
Page navigation among multiple pages is a common scenario in virtually
all Web applications. The following sample demonstrates how to use the <asp:hyperlink runat=server> control to navigate
to another page (passing custom query string parameters along the way). The
sample then demonstrates how to easily get access to these
query string parameters from the target page.
Not all page navigation scenarios are initiated through hyperlinks on the client.
Client-side page redirects or navigations can also be initiated from the
server by an ASP.NET page developer by calling the Response.Redirect(url) method.
This is typically done when server-side validation is required on some client
input before the navigation actually takes place.
The following sample demonstrates how to use the Response.Redirect
method to pass parameters to another target page. It also demonstrates how to easily get access to these parameters from the target
page.
VB Controls1.aspx
[Run Sample] |
[View Source]
Manipulating Server Controls
VB Controls2.aspx
[Run Sample] |
[View Source]
Handling Control Action Events
VB Controls3.aspx
[Run Sample] |
[View Source]
Handling Multiple Control Action Events
VB Controls4.aspx
[Run Sample] |
[View Source]
Performing Page Navigation (Scenario 1)
VB Controls5.aspx
[Run Sample] |
[View Source]
Performing Page Navigation (Scenario 2)
VB Controls6.aspx
[Run Sample] |
[View Source]