Tutorials

What You Should Already Know
Before you continue you should have a basic understanding of the following:
 WWW, HTML, XML and the basics of building Web pages

 Scripting languages like JavaScript or VBScript
 The basics of server side scripting like ASP or PHP
If you want to study these subjects first, find the tutorials on our Home Page
What is Classic ASP?

Microsoft's previous server side scripting technology ASP (Active Server Pages) is now often
called classic ASP.
ASP 3.0 was the last version of classic ASP.
To learn more about classic ASP, you can study our ASP tutorial.
ASP.NET is NOT ASP

ASP.NET is the next generation ASP, but it's not an upgraded version of ASP.
ASP.NET is an entirely new technology for server-side scripting. It was written from the ground
up and is not backward compatible with classic ASP.
You can read more about the differences between ASP and ASP.NET in the next chapter of this
tutorial.
ASP.NET is the major part of the Microsoft's .NET Framework.
What is ASP.NET?
ASP.NET is a server side scripting technology that enables scripts (embedded in web pages) to
be executed by an Internet server.
 ASP.NET is a Microsoft Technology

 ASP stands for Active Server Pages
 ASP.NET is a program that runs inside IIS
 IIS (Internet Information Services) is Microsoft's Internet server
 IIS comes as a free component with Windows servers
 IIS is also a part of Windows 2000 and XP Professional
What is an ASP.NET File?

 An ASP.NET file is just the same as an HTML file
 An ASP.NET file can contain HTML, XML, and scripts
 Scripts in an ASP.NET file are executed on the server
 An ASP.NET file has the file extension ".aspx"
How Does ASP.NET Work?

 When a browser requests an HTML file, the server returns the file
 When a browser requests an ASP.NET file, IIS passes the request to the ASP.NET engine
on the server
 The ASP.NET engine reads the file, line by line, and executes the scripts in the file
 Finally, the ASP.NET file is returned to the browser as plain HTML
What is ASP+?
ASP+ is the same as ASP.NET.
ASP+ is just an early name used by Microsoft when they developed ASP.NET.
The Microsoft .NET Framework

The .NET Framework is the infrastructure for the Microsoft .NET platform.
The .NET Framework is an environment for building, deploying, and running Web applications
and Web Services.
Microsoft's first server technology ASP (Active Server Pages), was a powerful and flexible
"programming language". But it was too code oriented. It was not an application framework and
not an enterprise development tool.
The Microsoft .NET Framework was developed to solve this problem.
.NET Frameworks keywords:

 Easier and quicker programming
 Reduced amount of code
 Declarative programming model
 Richer server control hierarchy with events
 Larger class library
 Better support for development tools
The .NET Framework consists of 3 main parts:
Programming languages:
 C# (Pronounced C sharp)
 Visual Basic (VB .NET)
 J# (Pronounced J sharp)
Server technologies and client technologies:
 ASP .NET (Active Server Pages)

 Windows Forms (Windows desktop solutions)
 Compact Framework (PDA / Mobile solutions)
Development environments:
 Visual Studio .NET (VS .NET)

 Visual Web Developer
This tutorial is about ASP.NET.
ASP.NET 2.0
ASP.NET 2.0 improves upon ASP.NET by adding support for several new features.
You can read more about the differences between ASP.NET 2.0 and ASP.NET in the next
chapter of this tutorial.
ASP.NET 3.0
ASP.NET 3.0 is not a new version of ASP.NET. It's just the name for a new ASP.NET 2.0
framework library with support for Windows Presentation Foundation, Windows
Communication Foundation, Windows Workflow Foundation; and Windows CardSpace.
ASP.NET 3.0 is not covered in this tutorial.
ASP.NET has better language support, a large set of new controls, XML-based components, and
better user authentication.
ASP.NET provides increased performance by running compiled code.
ASP.NET code is not fully backward compatible with ASP.
New in ASP.NET
 Better language support
 Programmable controls
 Event-driven programming
 XML-based components
 User authentication, with accounts and roles
 Higher scalability
 Increased performance - Compiled code
 Easier configuration and deployment
 Not fully ASP compatible
Language Support
ASP.NET uses ADO.NET.
ASP.NET supports full Visual Basic, not VBScript.
ASP.NET supports C# (C sharp) and C++.
ASP.NET supports JScript.
ASP.NET Controls
ASP.NET contains a large set of HTML controls. Almost all HTML elements on a page can be
defined as ASP.NET control objects that can be controlled by scripts.
ASP.NET also contains a new set of object-oriented input controls, like programmable list-boxes
and validation controls.
A new data grid control supports sorting, data paging, and everything you can expect from a
dataset control.
Event Aware Controls

All ASP.NET objects on a Web page can expose events that can be processed by ASP.NET
code.
Load, Click and Change events handled by code makes coding much simpler and much better
organized.
ASP.NET Components
ASP.NET components are heavily based on XML. Like the new AD Rotator, that uses XML to
store advertisement information and configuration.
User Authentication
ASP.NET supports form-based user authentication, cookie management, and automatic
redirecting of unauthorized logins.
User Accounts and Roles

ASP.NET allows user accounts and roles, to give each user (with a given role) access to different
server code and executables.
High Scalability
Much has been done with ASP.NET to provide greater scalability.
Server-to-server communication has been greatly enhanced, making it possible to scale an

application over several servers. One example of this is the ability to run XML parsers, XSL
transformations and even resource hungry session objects on other servers.
Compiled Code
The first request for an ASP.NET page on the server will compile the ASP.NET code and keep a
cached copy in memory. The result of this is greatly increased performance.
Easy Configuration
Configuration of ASP.NET is done with plain text files.
Configuration files can be uploaded or changed while the application is running. No need to
restart the server. No more metabase or registry puzzle.
Easy Deployment
No more server-restart to deploy or replace compiled code. ASP.NET simply redirects all new
requests to the new code.
Compatibility
ASP.NET is not fully compatible with earlier versions of ASP, so most of the old ASP code will
need some changes to run under ASP.NET.
To overcome this problem, ASP.NET uses a new file extension ".aspx". This will make
ASP.NET applications able to run side by side with standard ASP applications on the same
server.
What You Need

If you have a Beta version of ASP.NET installed, we recommend that you completely uninstall
it!
Or even better: start with a fresh Windows 2000 or XP installation!
Windows 2000 or XP
If you are serious about developing ASP.NET applications you should install Windows 2000
Professional or Windows XP Professional.
In both cases, install the Internet Information Services (IIS) from the Add/Remove Windows
components dialog.
Service Packs and Updates

Before ASP.NET can be installed on your computer, all relevant service packs and security
updates must be installed.
The easiest way to do this is to activate your Windows Internet Update. When you access the
Windows Update page, you will be instructed to install the latest service packs and all critical
security updates. For Windows 2000, make sure you install Service Pack 2. You should also
install the latest version of Internet Explorer.
Tip: Read the note about connection speed and download time at the bottom of this page.
Install .NET
From your Windows Update you can now select the Microsoft .NET Framework.
After download, the .NET framework will install itself on your computer - there are no options to
select for installation.
You are now ready to develop your first ASP.NET application!
The .NET Software Development Kit

If you have the necessary bandwidth, you might consider downloading the full Microsoft .NET
Software Development Kit (SDK).
We fully recommend getting the SDK for learning more about .NET, and for the documentation,
samples, and tools included.
Connection Speed and Download Time

If you have a slow Internet connection, you might have problems downloading large files like the
Windows 2000 Service Pack 2 and the Microsoft .NET Framework.
If download speed is a problem, our best suggestion is to get the latest files from someone else,
from a colleague, from a friend, or from one of the CDs that comes with many popular computer
magazines.
A simple ASP.NET page looks just like an ordinary HTML page.
Hello W3Schools
To start learning ASP.NET, we will construct a very simple HTML page that will display "Hello
W3Schools" in an Internet browser like this:
Hello W3Schools!

Hello W3Schools in HTML

This code displays the example as an HTML page:
<html>
<body bgcolor="yellow">
<center>
<h2>Hello W3Schools!</h2>
</center>
</body>
</html>
If you want to try it yourself, save the code in a file called "firstpage.htm", and create a link to
the file like this: firstpage.htm
Hello W3Schools in ASP.NET

The simplest way to convert an HTML page into an ASP.NET page is to copy the HTML file to
a new file with an .aspx extension.
This code displays our example as an ASP.NET page:
<html>
<center>
</center>
</body>
</html>
If you want to try it yourself, save the code in a file called "firstpage.aspx", and create a link to
the file like this: firstpage.aspx
How Does it Work?

Fundamentally an ASP.NET page is just the same as an HTML page.
An HTML page has the extension .htm. If a browser requests an HTML page from the server, the
server sends the page to the browser without any modifications.
An ASP.NET page has the extension .aspx. If a browser requests an ASP.NET page, the server
processes any executable code in the page, before the result is sent back to the browser.
The ASP.NET page above does not contain any executable code, so nothing is executed. In the
next examples we will add some executable code to the page to demonstrate the difference
between static HTML pages and dynamic ASP pages.
Classic ASP
Active Server Pages (ASP) has been around for several years. With ASP, executable code can be
placed inside HTML pages.
Previous versions of ASP (before ASP .NET) are often called Classic ASP.
ASP.NET is not fully compatible with Classic ASP, but most Classic ASP pages will work fine
as ASP.NET pages, with only minor changes.
If you want to learn more about Classic ASP, please visit our ASP Tutorial.
Dynamic Page in Classic ASP
To demonstrate how ASP can display pages with dynamic content, we have added some
executable code (in red) to the previous example:
<html>
<center>
<p><%Response.Write(now())%></p>
</center>
</body>
</html>
The code inside the <% --%> tags is executed on the server.
Response.Write is ASP code for writing something to the HTML output stream.
Now() is a function returning the servers current date and time.
If you want to try it yourself, save the code in a file called "dynpage.asp", and create a link to
the file like this: dynpage.asp
Dynamic Page in ASP .NET

This following code displays our example as an ASP.NET page:
<html>
<center>
</center>
</body>
</html>
If you want to try it yourself, save the code in a file called "dynpage.aspx", and create a link to
the file like this: dynpage.aspx
ASP.NET vs Classic ASP
The previous examples didn't demonstrate any differences between ASP.NET and Classic ASP.
As you can see from the two latest examples there are no differences between the two ASP and
ASP.NET pages.
In the next chapters you will see how server controls make ASP.NET more powerful than
Classic ASP.
Limitations in Classic ASP

The listing below was copied from the previous chapter:
<html>
<center>
</center>
</body>
</html>
The code above illustrates a limitation in Classic ASP: The code block has to be placed where
you want the output to appear.
With Classic ASP it is impossible to separate executable code from the HTML itself. This makes
the page difficult to read, and difficult to maintain.
ASP.NET - Server Controls

ASP.NET has solved the "spaghetti-code" problem described above with server controls.
Server controls are tags that are understood by the server.
There are three kinds of server controls:
 HTML Server Controls - Traditional HTML tags

 Web Server Controls - New ASP.NET tags
 Validation Server Controls - For input validation
ASP.NET - HTML Server Controls
HTML server controls are HTML tags understood by the server.
HTML elements in ASP.NET files are, by default, treated as text. To make these elements
programmable, add a runat="server" attribute to the HTML element. This attribute indicates that
the element should be treated as a server control. The id attribute is added to identify the server
control. The id reference can be used to manipulate the server control at run time.
Note: All HTML server controls must be within a <form> tag with the runat="server" attribute.
The runat="server" attribute indicates that the form should be processed on the server. It also
indicates that the enclosed controls can be accessed by server scripts.
In the following example we declare an HtmlAnchor server control in an .aspx file. Then we
manipulate the HRef attribute of the HtmlAnchor control in an event handler (an event handler is
a subroutine that executes code for a given event). The Page_Load event is one of many events
that ASP.NET understands:
<script runat="server">
Sub Page_Load
link1.HRef="http://www.w3schools.com"
End Sub
</script>
<html>
<body>
<form runat="server">
<a id="link1" runat="server">Visit W3Schools!</a>
</form>
</body>
</html>
The executable code itself has been moved outside the HTML.
ASP.NET - Web Server Controls

Web server controls are special ASP.NET tags understood by the server.
Like HTML server controls, Web server controls are also created on the server and they require a
runat="server" attribute to work. However, Web server controls do not necessarily map to any
existing HTML elements and they may represent more complex elements.
The syntax for creating a Web server control is:
<asp:control_name id="some_id" runat="server" />
In the following example we declare a Button server control in an .aspx file. Then we create an
event handler for the Click event which changes the text on the button:
Sub submit(Source As Object, e As EventArgs)
button1.Text="You clicked me!"
End Sub
</script>
<html>
<body>
<asp:Button id="button1" Text="Click me!"
runat="server" OnClick="submit"/>
</form>
</body>
</html>
ASP.NET - Validation Server Controls

Validation server controls are used to validate user-input. If the user-input does not pass
validation, it will display an error message to the user.
Each validation control performs a specific type of validation (like validating against a specific
value or a range of values).
By default, page validation is performed when a Button, ImageButton, or LinkButton control is

clicked. You can prevent validation when a button control is clicked by setting the
CausesValidation property to false.
The syntax for creating a Validation server control is:
In the following example we declare one TextBox control, one Button control, and one
RangeValidator control in an .aspx file. If validation fails, the text "The value must be from 1 to
100!" will be displayed in the RangeValidator control:
Example
<html>
<body>
<p>Enter a number from 1 to 100:
<asp:TextBox id="tbox1" runat="server" />
<br /><br />
<asp:Button Text="Submit" runat="server" />
</p>
<p>
<asp:RangeValidator
ControlToValidate="tbox1"
MinimumValue="1"
MaximumValue="100"
Type="Integer"
Text="The value must be from 1 to 100!"
runat="server" />
</p>
</form>
</body>
</html>
ASP.NET - Event Handlers

Look at the following code:
<%
lbl1.Text="The date and time is " & now()
%>
<html>
<body>
<h3><asp:label id="lbl1" runat="server" /></h3>
</form>
</body>
</html>
When will the code above be executed? The answer is: "You don't know..."
The Page_Load Event
The Page_Load event is one of many events that ASP.NET understands. The Page_Load event is
triggered when a page loads, and ASP.NET will automatically call the subroutine Page_Load,
and execute the code inside it:
Example
Sub Page_Load
End Sub
</script>
<html>
<body>
</form>
</body>
</html>
Show example »
Note: The Page_Load event contains no object references or event arguments!
The Page.IsPostBack Property

The Page_Load subroutine runs EVERY time the page is loaded. If you want to execute the code
in the Page_Load subroutine only the FIRST time the page is loaded, you can use the
Page.IsPostBack property. If the Page.IsPostBack property is false, the page is loaded for the
first time, if it is true, the page is posted back to the server (i.e. from a button click on a form):
Example
Sub Page_Load
if Not Page.IsPostBack then
end if
End Sub
Sub submit(s As Object, e As EventArgs)
lbl2.Text="Hello World!"
End Sub
</script>
<html>
<body>
<asp:button text="Submit" onclick="submit" runat="server" />
</form>
</body>
</html>
Show example »
The example above will write the "The date and time is...." message only the first time the page
is loaded. When a user clicks on the Submit button, the submit subroutine will write "Hello
World!" to the second label, but the date and time in the first label will not change.
All server controls must appear within a <form> tag, and the <form> tag must contain the
runat="server" attribute.
ASP.NET Web Forms

All server controls must appear within a <form> tag, and the <form> tag must contain the
runat="server" attribute. The runat="server" attribute indicates that the form should be processed
on the server. It also indicates that the enclosed controls can be accessed by server scripts:
...HTML + server controls
</form>
Note: The form is always submitted to the page itself. If you specify an action attribute, it is
ignored. If you omit the method attribute, it will be set to method="post" by default. Also, if you
do not specify the name and id attributes, they are automatically assigned by ASP.NET.
Note: An .aspx page can only contain ONE <form runat="server"> control!
If you select view source in an .aspx page containing a form with no name, method, action, or id
attribute specified, you will see that ASP.NET has added these attributes to the form. It looks
something like this:
<form name="_ctl0" method="post" action="page.aspx" id="_ctl0">
...some code
</form>
Submitting a Form
A form is most often submitted by clicking on a button. The Button server control in ASP.NET
has the following format:
<asp:Button id="id" text="label" OnClick="sub" runat="server" />
The id attribute defines a unique name for the button and the text attribute assigns a label to the
button. The onClick event handler specifies a named subroutine to execute.
In the following example we declare a Button control in an .aspx file. A button click runs a
subroutine which changes the text on the button:
You may save a lot of coding by maintaining the ViewState of the objects in your Web Form.
Maintaining the ViewState

When a form is submitted in classic ASP, all form values are cleared. Suppose you have
submitted a form with a lot of information and the server comes back with an error. You will
have to go back to the form and correct the information. You click the back button, and what
happens.......ALL form values are CLEARED, and you will have to start all over again! The site
did not maintain your ViewState.
When a form is submitted in ASP .NET, the form reappears in the browser window together with
all form values. How come? This is because ASP .NET maintains your ViewState. The
ViewState indicates the status of the page when submitted to the server. The status is defined
through a hidden field placed on each page with a <form runat="server"> control. The source
could look something like this:
<form name="_ctl0" method="post" action="page.aspx" id="_ctl0">

<input type="hidden" name="__VIEWSTATE"
value="dDwtNTI0ODU5MDE1Ozs+ZBCF2ryjMpeVgUrY2eTj79HNl4Q=" />
.....some code
</form>
Maintaining the ViewState is the default setting for ASP.NET Web Forms. If you want to NOT
maintain the ViewState, include the directive <%@ Page EnableViewState="false" %> at the top
of an .aspx page or add the attribute EnableViewState="false" to any control.
Look at the following .aspx file. It demonstrates the "old" way to do it. When you click on the
submit button, the form value will disappear:
Example
<html>
<body>
<form action="demo_classicasp.aspx" method="post">

Your name: <input type="text" name="fname" size="20">
<input type="submit" value="Submit">
</form>
<%
dim fname
fname=Request.Form("fname")
If fname<>"" Then
Response.Write("Hello " & fname & "!")
End If
%>
</body>
</html>
Show example »
Here is the new ASP .NET way. When you click on the submit button, the form value will NOT
disappear:
Example
Click view source in the right frame of the example to see that ASP .NET has added a hidden
field in the form to maintain the ViewState
Sub submit(sender As Object, e As EventArgs)
lbl1.Text="Hello " & txt1.Text & "!"
End Sub
</script>
<html>
<body>
Your name: <asp:TextBox id="txt1" runat="server" />
<asp:Button OnClick="submit" Text="Submit" runat="server" />
<p><asp:Label id="lbl1" runat="server" /></p>
</form>
</body>
</html>
The TextBox control is used to create a text box where the user can input text.
The TextBox Control

The TextBox control is used to create a text box where the user can input text.
The TextBox control's attributes and properties are listed in our web controls reference page.
The example below demonstrates some of the attributes you may use with the TextBox control:
Example
<html>
<body>
A basic TextBox:
<asp:TextBox id="tb1" runat="server" />
<br /><br />
A password TextBox:
<asp:TextBox id="tb2" TextMode="password" runat="server" />
<br /><br />
A TextBox with text:

<asp:TextBox id="tb4" Text="Hello World!" runat="server" />
<br /><br />
A multiline TextBox:
<asp:TextBox id="tb3" TextMode="multiline" runat="server" />
<br /><br />
A TextBox with height:

<asp:TextBox id="tb6" rows="5" TextMode="multiline"
runat="server" />
<br /><br />
A TextBox with width:

<asp:TextBox id="tb5" columns="30" runat="server" />
</form>
</body>
</html>
Show example »
Add a Script
The contents and settings of a TextBox control may be changed by server scripts when a form is
submitted. A form can be submitted by clicking on a button or when a user changes the value in
the TextBox control.
In the following example we declare one TextBox control, one Button control, and one Label
control in an .aspx file. When the submit button is triggered, the submit subroutine is executed.
The submit subroutine writes a text to the Label control:
Example
lbl1.Text="Your name is " & txt1.Text
End Sub
</script>
<html>
<body>
Enter your name:
<asp:TextBox id="txt1" runat="server" />
</form>
</body>
</html>
Show example »
In the following example we declare one TextBox control and one Label control in an .aspx file.
When you change the value in the TextBox and either click outside the TextBox or press the Tab
key, the change subroutine is executed. The submit subroutine writes a text to the Label control:
Example
Sub change(sender As Object, e As EventArgs)
lbl1.Text="You changed text to " & txt1.Text
End Sub
</script>
<html>
<body>
Enter your name:
<asp:TextBox id="txt1" runat="server"
text="Hello World!"
ontextchanged="change" autopostback="true"/>
</form>
</body>
</html>
The Button control is used to display a push button.
The Button Control

The Button control is used to display a push button. The push button may be a submit button or a
command button. By default, this control is a submit button.
A submit button does not have a command name and it posts the page back to the server when it
is clicked. It is possible to write an event handler to control the actions performed when the
submit button is clicked.
A command button has a command name and allows you to create multiple Button controls on a
page. It is possible to write an event handler to control the actions performed when the command
button is clicked.
The Button control's attributes and properties are listed in our web controls reference page.
The example below demonstrates a simple Button control:
<html>
<body>
<asp:Button id="b1" Text="Submit" runat="server" />
</form>
</body>
</html>
Add a Script
A form is most often submitted by clicking on a button.
In the following example we declare one TextBox control, one Button control, and one Label
control in an .aspx file. When the submit button is triggered, the submit subroutine is executed.
The submit subroutine writes a text to the Label control:
Example
lbl1.Text="Your name is " & txt1.Text
End Sub
</script>
<html>
<body>
Enter your name:
<asp:TextBox id="txt1" runat="server" />
</form>
</body>
</html>
We may use data binding to fill lists with selectable items from an imported data source, like a
database, an XML file, or a script.
Data Binding
The following controls are list controls which support data binding:
 asp:RadioButtonList
 asp:CheckBoxList
 asp:DropDownList
 asp:Listbox
The selectable items in each of the above controls are usually defined by one or more
asp:ListItem controls, like this:
<html>
<body>
<asp:RadioButtonList id="countrylist" runat="server">
<asp:ListItem value="N" text="Norway" />
<asp:ListItem value="S" text="Sweden" />
<asp:ListItem value="F" text="France" />
<asp:ListItem value="I" text="Italy" />
</asp:RadioButtonList>
</form>
</body>
</html>
However, with data binding we may use a separate source, like a database, an XML file, or a
script to fill the list with selectable items.
By using an imported source, the data is separated from the HTML, and any changes to the items
are made in the separate data source.
In the next three chapters, we will describe how to bind data from a scripted data source.
Create an ArrayList
The ArrayList object is a collection of items containing a single data value.
Items are added to the ArrayList with the Add() method.
The following code creates a new ArrayList object named mycountries and four items are added:
Sub Page_Load
dim mycountries=New ArrayList
mycountries.Add("Norway")
mycountries.Add("Sweden")
mycountries.Add("France")
mycountries.Add("Italy")
end if
end sub
</script>
By default, an ArrayList object contains 16 entries. An ArrayList can be sized to its final size
with the TrimToSize() method:
Sub Page_Load
mycountries.TrimToSize()
end if
end sub
</script>
An ArrayList can also be sorted alphabetically or numerically with the Sort() method:
Sub Page_Load
mycountries.Sort()
end if
end sub
</script>
To sort in reverse order, apply the Reverse() method after the Sort() method:
Sub Page_Load
mycountries.Sort()
mycountries.Reverse()
end if
end sub
</script>
Data Binding to an ArrayList

An ArrayList object may automatically generate the text and values to the following controls:
 asp:Listbox
To bind data to a RadioButtonList control, first create a RadioButtonList control (without any
asp:ListItem elements) in an .aspx page:
<html>
<body>
<asp:RadioButtonList id="rb" runat="server" />
</form>
</body>
</html>
Then add the script that builds the list and binds the values in the list to the RadioButtonList
control:
Example
Sub Page_Load
mycountries.Sort()
rb.DataSource=mycountries
rb.DataBind()
end if
end sub
</script>
<html>
<body>
<asp:RadioButtonList id="rb" runat="server" />
</form>
</body>
</html>
XML Files
asp:Repeater
asp:DataList
ASP.NET Database
.NET DB Connection
ASP.NET 2.0
2.0 New Features
2.0 Master Pages
2.0 Navigation
ASP.NET References
HTML Controls
Web Controls
Validation Controls
ASP.NET Examples
ASP.NET Examples
ASP.NET - The Hashtable Object
« Previous Next Chapter »
The Hashtable object contains items in key/value pairs.
Try it Yourself - Examples

Hashtable RadiobuttonList 1
Hashtable RadiobuttonList 2
Hashtable DropDownList
Create a Hashtable
The Hashtable object contains items in key/value pairs. The keys are used as indexes,
and very quick searches can be made for values by searching through their keys.
Items are added to the Hashtable with the Add() method.
The following code creates a Hashtable named mycountries and four elements are
added:
Sub Page_Load
dim mycountries=New Hashtable
mycountries.Add("N","Norway")
mycountries.Add("S","Sweden")
mycountries.Add("F","France")
mycountries.Add("I","Italy")
end if
end sub
</script>
Data Binding
A Hashtable object may automatically generate the text and values to the following
controls:
 asp:Listbox
To bind data to a RadioButtonList control, first create a RadioButtonList control

(without any asp:ListItem elements) in an .aspx page:
<html>
<body>
<asp:RadioButtonList id="rb" runat="server" AutoPostBack="True" />
</form>
</body>
</html>
Then add the script that builds the list:
sub Page_Load
rb.DataValueField="Key"
rb.DataTextField="Value"
rb.DataBind()
end if
end sub
</script>
<html>
<body>
</form>
</body>
</html>
Then we add a sub routine to be executed when the user clicks on an item in the
RadioButtonList control. When a radio button is clicked, a text will appear in a label:
Example
sub Page_Load
rb.DataBind()
end if
end sub
sub displayMessage(s as Object,e As EventArgs)

lbl1.text="Your favorite country is: " & rb.SelectedItem.Text
end sub
</script>
<html>
<body>
<asp:RadioButtonList id="rb" runat="server"
AutoPostBack="True" onSelectedIndexChanged="displayMessage" />
<p><asp:label id="lbl1" runat="server" /></p>
</form>
</body>
</html>
The SortedList Object

The SortedList object contains items in key/value pairs. A SortedList object automatically sort
the items in alphabetic or numeric order.
Items are added to the SortedList with the Add() method. A SortedList can be sized to its final
size with the TrimToSize() method.
The following code creates a SortedList named mycountries and four elements are added:
sub Page_Load
dim mycountries=New SortedList
end if
end sub
</script>
Data Binding
A SortedList object may automatically generate the text and values to the following controls:
 asp:Listbox
To bind data to a RadioButtonList control, first create a RadioButtonList control (without any
asp:ListItem elements) in an .aspx page:
<html>
<body>
</form>
</body>
</html>
Then add the script that builds the list:
sub Page_Load
rb.DataBind()
end if
end sub
</script>
<html>
<body>
</form>
</body>
</html>
Then we add a sub routine to be executed when the user clicks on an item in the RadioButtonList
control. When a radio button is clicked, a text will appear in a label:
Example
sub Page_Load
rb.DataBind()
end if
end sub

end sub
</script>
<html>
<body>
</form>
</body>
</html>
We can bind an XML file to a list control.
An XML File
Here is an XML file named "countries.xml":
<?xml version="1.0" encoding="ISO-8859-1"?>
<countries>
<country>
<text>Norway</text>
<value>N</value>
</country>
<country>
<text>Sweden</text>
<value>S</value>
</country>
<country>
<text>France</text>
<value>F</value>
</country>
<country>
<text>Italy</text>
<value>I</value>
</country>
</countries>
Take a look at the XML file: countries.xml
Bind a DataSet to a List Control

First, import the "System.Data" namespace. We need this namespace to work with DataSet
objects. Include the following directive at the top of an .aspx page:
<%@ Import Namespace="System.Data" %>
Next, create a DataSet for the XML file and load the XML file into the DataSet when the page is
first loaded:
sub Page_Load
dim mycountries=New DataSet
mycountries.ReadXml(MapPath("countries.xml"))
end if
end sub
To bind the DataSet to a RadioButtonList control, first create a RadioButtonList control (without
any asp:ListItem elements) in an .aspx page:
<html>
<body>
</form>
</body>
</html>
Then add the script that builds the XML DataSet:
sub Page_Load
rb.DataValueField="value"
rb.DataTextField="text"
rb.DataBind()
end if
end sub
</script>
<html>
<body>
</form>
</body>
</html>
Then we add a sub routine to be executed when the user clicks on an item in the RadioButtonList
control. When a radio button is clicked, a text will appear in a label:
Example
sub Page_Load
rb.DataValueField="value"
rb.DataTextField="text"
rb.DataBind()
end if
end sub

end sub
</script>
<html>
<body>
</form>
</body>
</html>
The Repeater control is used to display a repeated list of items that are bound to the control.
Bind a DataSet to a Repeater Control

The Repeater control is used to display a repeated list of items that are bound to the control. The
Repeater control may be bound to a database table, an XML file, or another list of items. Here
we will show how to bind an XML file to a Repeater control.
We will use the following XML file in our examples ("cdcatalog.xml"):
<catalog>
<cd>
<title>Empire Burlesque</title>
<artist>Bob Dylan</artist>
<country>USA</country>
<company>Columbia</company>
<price>10.90</price>
<year>1985</year>
</cd>
<cd>
<title>Hide your heart</title>
<artist>Bonnie Tyler</artist>
<country>UK</country>
<company>CBS Records</company>
<price>9.90</price>
<year>1988</year>
</cd>
<cd>
<title>Greatest Hits</title>
<artist>Dolly Parton</artist>
<company>RCA</company>
<price>9.90</price>
<year>1982</year>
</cd>
<cd>
<title>Still got the blues</title>
<artist>Gary Moore</artist>
<company>Virgin records</company>
<year>1990</year>
</cd>
<cd>
<title>Eros</title>
<artist>Eros Ramazzotti</artist>
<country>EU</country>
<company>BMG</company>
<price>9.90</price>
<year>1997</year>
</cd>
</catalog>
Take a look at the XML file: cdcatalog.xml
first loaded:
sub Page_Load
dim mycdcatalog=New DataSet
mycdcatalog.ReadXml(MapPath("cdcatalog.xml"))
end if
end sub
Then we create a Repeater control in an .aspx page. The contents of the <HeaderTemplate>
element are rendered first and only once within the output, then the contents of the
<ItemTemplate> element are repeated for each "record" in the DataSet, and last, the contents of
the <FooterTemplate> element are rendered once within the output:
<html>
<body>
<asp:Repeater id="cdcatalog" runat="server">
<HeaderTemplate>
...
</HeaderTemplate>
<ItemTemplate>
...
</ItemTemplate>
<FooterTemplate>
...
</FooterTemplate>
</asp:Repeater>
</form>
</body>
</html>
Then we add the script that creates the DataSet and binds the mycdcatalog DataSet to the
Repeater control. We also fill the Repeater control with HTML tags and bind the data items to
the cells in the<ItemTemplate> section with the <%#Container.DataItem("fieldname")%>
method:
Example
sub Page_Load
cdcatalog.DataSource=mycdcatalog
cdcatalog.DataBind()
end if
end sub
</script>
<html>
<body>
<HeaderTemplate>
<table border="1" width="100%">
<tr>
<th>Title</th>
<th>Artist</th>
<th>Country</th>
<th>Company</th>
<th>Price</th>
<th>Year</th>
</tr>
</HeaderTemplate>
<ItemTemplate>
<tr>
<td><%#Container.DataItem("title")%></td>
<td><%#Container.DataItem("artist")%></td>
<td><%#Container.DataItem("country")%></td>
<td><%#Container.DataItem("company")%></td>
<td><%#Container.DataItem("price")%></td>
<td><%#Container.DataItem("year")%></td>
</tr>
</ItemTemplate>
<FooterTemplate>
</table>
</FooterTemplate>
</asp:Repeater>
</form>
</body>
</html>
Show example »
Using the <AlternatingItemTemplate>

You can add an <AlternatingItemTemplate> element after the <ItemTemplate> element to
describe the appearance of alternating rows of output. In the following example each other row
in the table will be displayed in a light grey color:
Example
sub Page_Load
end if
end sub
</script>
<html>
<body>
<HeaderTemplate>
<tr>
<th>Title</th>
<th>Artist</th>
<th>Country</th>
<th>Company</th>
<th>Price</th>
<th>Year</th>
</tr>
</HeaderTemplate>
<ItemTemplate>
<tr>
</tr>
</ItemTemplate>
<AlternatingItemTemplate>
<tr bgcolor="#e8e8e8">
</tr>
</AlternatingItemTemplate>
<FooterTemplate>
</table>
</FooterTemplate>
</asp:Repeater>
</form>
</body>
</html>
Show example »
Using the <SeparatorTemplate>

The <SeparatorTemplate> element can be used to describe a separator between each record. The
following example inserts a horizontal line between each table row:
Example
sub Page_Load
end if
end sub
</script>
<html>
<body>
<HeaderTemplate>
<tr>
<th>Title</th>
<th>Artist</th>
<th>Country</th>
<th>Company</th>
<th>Price</th>
<th>Year</th>
</tr>
</HeaderTemplate>
<ItemTemplate>
<tr>
</tr>
</ItemTemplate>
<SeparatorTemplate>
<tr>
<td colspan="6"><hr /></td>
</tr>
</SeparatorTemplate>
<FooterTemplate>
</table>
</FooterTemplate>
</asp:Repeater>
</form>
</body>
</html>
The DataList control is, like the Repeater control, used to display a repeated list of items that are
bound to the control. However, the DataList control adds a table around the data items by
default.
Bind a DataSet to a DataList Control

The DataList control is, like the Repeater control, used to display a repeated list of items that are
bound to the control. However, the DataList control adds a table around the data items by
default. The DataList control may be bound to a database table, an XML file, or another list of
items. Here we will show how to bind an XML file to a DataList control.
We will use the following XML file in our examples ("cdcatalog.xml"):
<catalog>
<cd>
<title>Empire Burlesque</title>
<artist>Bob Dylan</artist>
<company>Columbia</company>
<year>1985</year>
</cd>
<cd>
<title>Hide your heart</title>
<artist>Bonnie Tyler</artist>
<company>CBS Records</company>
<price>9.90</price>
<year>1988</year>
</cd>
<cd>
<title>Greatest Hits</title>
<artist>Dolly Parton</artist>
<company>RCA</company>
<price>9.90</price>
<year>1982</year>
</cd>
<cd>
<title>Still got the blues</title>
<artist>Gary Moore</artist>
<company>Virgin records</company>
<year>1990</year>
</cd>
<cd>
<title>Eros</title>
<artist>Eros Ramazzotti</artist>
<country>EU</country>
<company>BMG</company>
<price>9.90</price>
<year>1997</year>
</cd>
</catalog>
Take a look at the XML file: cdcatalog.xml
first loaded:
sub Page_Load
end if
end sub
Then we create a DataList in an .aspx page. The contents of the <HeaderTemplate> element are
rendered first and only once within the output, then the contents of the <ItemTemplate> element
are repeated for each "record" in the DataSet, and last, the contents of the <FooterTemplate>
element are rendered once within the output:
<html>
<body>
<asp:DataList id="cdcatalog" runat="server">
<HeaderTemplate>
...
</HeaderTemplate>
<ItemTemplate>
...
</ItemTemplate>
<FooterTemplate>
...
</FooterTemplate>
</asp:DataList>
</form>
</body>
</html>
Then we add the script that creates the DataSet and binds the mycdcatalog DataSet to the
DataList control. We also fill the DataList control with a <HeaderTemplate> that contains the
header of the table, an <ItemTemplate> that contains the data items to display, and a
<FooterTemplate> that contains a text. Note that the gridlines attribute of the DataList is set to
"both" to display table borders:
Example
sub Page_Load
end if
end sub
</script>
<html>
<body>
<asp:DataList id="cdcatalog"
gridlines="both" runat="server">
<HeaderTemplate>
My CD Catalog
</HeaderTemplate>
<ItemTemplate>
"<%#Container.DataItem("title")%>" of
<%#Container.DataItem("artist")%> -
$<%#Container.DataItem("price")%>
</ItemTemplate>
<FooterTemplate>
Copyright Hege Refsnes
</FooterTemplate>
</asp:DataList>
</form>
</body>
</html>
Show example »
Using Styles
You can also add styles to the DataList control to make the output more fancy:
Example
sub Page_Load
end if
end sub
</script>
<html>
<body>
runat="server"
cellpadding="2"
cellspacing="2"
borderstyle="inset"
backcolor="#e8e8e8"
width="100%"
headerstyle-font-name="Verdana"
headerstyle-font-size="12pt"
headerstyle-horizontalalign="center"
headerstyle-font-bold="true"
itemstyle-backcolor="#778899"
itemstyle-forecolor="#ffffff"
footerstyle-font-size="9pt"
footerstyle-font-italic="true">
<HeaderTemplate>
My CD Catalog
</HeaderTemplate>
<ItemTemplate>
</ItemTemplate>
<FooterTemplate>
Copyright Hege Refsnes
</FooterTemplate>
</asp:DataList>
</form>
</body>
</html>
Show example »
Using the <AlternatingItemTemplate>
You can add an <AlternatingItemTemplate> element after the <ItemTemplate> element to
describe the appearance of alternating rows of output. You may style the data in the
<AlternatingItemTemplate> section within the DataList control:
Example
sub Page_Load
end if
end sub
</script>
<html>
<body>
runat="server"
cellpadding="2"
cellspacing="2"
borderstyle="inset"
backcolor="#e8e8e8"
width="100%"
headerstyle-font-name="Verdana"
headerstyle-font-size="12pt"
headerstyle-horizontalalign="center"
headerstyle-font-bold="True"
itemstyle-backcolor="#778899"
itemstyle-forecolor="#ffffff"
alternatingitemstyle-backcolor="#e8e8e8"
alternatingitemstyle-forecolor="#000000"
footerstyle-font-size="9pt"
footerstyle-font-italic="True">
<HeaderTemplate>
My CD Catalog
</HeaderTemplate>
<ItemTemplate>
</ItemTemplate>
<AlternatingItemTemplate>
</AlternatingItemTemplate>
<FooterTemplate>
© Hege Refsnes
</FooterTemplate>
</asp:DataList>
</form>
</body>
</html>
ADO.NET is also a part of the .NET Framework. ADO.NET is used to handle data access. With
ADO.NET you can work with databases.
Try it Yourself - Examples
Database connection - Bind to a DataList control
Database connection - Bind to a Repeater control
What is ADO.NET?
 ADO.NET is a part of the .NET Framework
 ADO.NET consists of a set of classes used to handle data access
 ADO.NET is entirely based on XML
 ADO.NET has, unlike ADO, no Recordset object
Create a Database Connection
We are going to use the Northwind database in our examples.
First, import the "System.Data.OleDb" namespace. We need this namespace to work with
Microsoft Access and other OLE DB database providers. We will create the connection to the
database in the Page_Load subroutine. We create a dbconn variable as a new OleDbConnection
class with a connection string which identifies the OLE DB provider and the location of the
database. Then we open the database connection:
<%@ Import Namespace="System.Data.OleDb" %>
sub Page_Load
dim dbconn
dbconn=New OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;
data source=" & server.mappath("northwind.mdb"))
dbconn.Open()
end sub
</script>
Note: The connection string must be a continuous string without a line break!
Create a Database Command

To specify the records to retrieve from the database, we will create a dbcomm variable as a new
OleDbCommand class. The OleDbCommand class is for issuing SQL queries against database
tables:
sub Page_Load
dim dbconn,sql,dbcomm
dbconn.Open()
sql="SELECT * FROM customers"
dbcomm=New OleDbCommand(sql,dbconn)
end sub
</script>
Create a DataReader
The OleDbDataReader class is used to read a stream of records from a data source. A
DataReader is created by calling the ExecuteReader method of the OleDbCommand object:
sub Page_Load
dim dbconn,sql,dbcomm,dbread
dbconn.Open()
dbread=dbcomm.ExecuteReader()
end sub
</script>
Bind to a Repeater Control

Then we bind the DataReader to a Repeater control:
Example
sub Page_Load
dim dbconn,sql,dbcomm,dbread
dbconn.Open()
dbread=dbcomm.ExecuteReader()
customers.DataSource=dbread
customers.DataBind()
dbread.Close()
dbconn.Close()
end sub
</script>
<html>
<body>
<asp:Repeater id="customers" runat="server">
<HeaderTemplate>
<tr>
<th>Companyname</th>
<th>Contactname</th>
<th>Address</th>
<th>City</th>
</tr>
</HeaderTemplate>
<ItemTemplate>
<tr>
<td><%#Container.DataItem("companyname")%></td>
<td><%#Container.DataItem("contactname")%></td>
<td><%#Container.DataItem("address")%></td>
<td><%#Container.DataItem("city")%></td>
</tr>
</ItemTemplate>
<FooterTemplate>
</table>
</FooterTemplate>
</asp:Repeater>
</form>
</body>
</html>
Close the Database Connection

Always close both the DataReader and database connection after access to the database is no
longer required:
dbread.Close()
dbconn.Close()
ASP.NET 2.0 improves ASP.NET by adding several new features.

Improvements in ASP.NET 2.0
ASP.NET 2.0 was designed to make web development easier and quicker.
Design goals for ASP.NET 2.0:
 Increase productivity by removing 70% of the code

 Use the same controls for all types of devices
 Provide a faster and better web server platform
 Simplify compilation and installation
 Simplify the administration of web applications
What's New in ASP.NET 2.0?

Some of the new features in ASP.NET 2.0 are:
 Master Pages, Themes, and Web Parts

 Standard controls for navigation
 Standard controls for security
 Roles, personalization, and internationalization services
 Improved and simplified data access controls
 Full support for XML standards like, XHTML, XML, and WSDL
 Improved compilation and deployment (installation)
 Improved site management
 New and improved development tools
The new features are described below.
Master Pages
ASP.NET didn't have a method for applying a consistent look and feel for a whole web site.
Master pages in ASP.NET 2.0 solves this problem.
A master page is a template for other pages, with shared layout and functionality. The master
page defines placeholders for content pages. The result page is a combination (merge) of the
master page and the content page.
Read more about master pages.
Themes
Themes is another feature of ASP.NET 2.0. Themes, or skins, allow developers to create a
customized look for web applications.
Design goals for ASP.NET 2.0 themes:
 Make it simple to customize the appearance of a site

 Allow themes to be applied to controls, pages, and entire sites
 Allow all visual elements to be customized
Web Parts
ASP.NET 2.0 Web Parts can provide a consistent look for a site, while still allowing user
customization of style and content.
New controls:
 Zone controls - areas on a page where the content is consistent

 Web part controls - content areas for each zone
Navigation
ASP.NET 2.0 has built-in navigation controls like
 Site Maps
 Dynamic HTML menus
 Tree Views
Security
Security is very important for protecting confidential and personal information.
In ASP.NET 2.0 the following controls has been added:

 A Login control, which provides login functionality
 A LoginStatus control, to control the login status
 A LoginName control to display the current user name
 A LoginView control, to provide different views depending on login status
 A CreateUser wizard, to allow creation of user accounts
 A PasswordRecovery control, to provide the "I forgot my password" functionality
Roles and Personalization

Internet communities are growing very popular.
ASP.NET 2.0 has personalization features for storing user details. This provides an easy way to
customize user (and user group) properties.
Internationalization
Reaching people with different languages is important if you want to reach a larger audience.
ASP.NET 2.0 has improved support for multiple languages.
Data Access
Many web sites are data driven, using databases or XML files as data sources.
With ASP.NET this involved code, and often the same code had to be used over and over in
different web pages.
A key goal of ASP.NET 2.0 was to ease the use of data sources.
ASP.NET 2.0 has new data controls, removing much of the need for programming and in-depth
knowledge of data connections.
Mobility Support
The problem with Mobile devices is screen size and display capabilities.
In ASP.NET, the Microsoft Mobile Internet Toolkit (MMIT) provided this support.
In ASP.NET 2.0, MMIT is no longer needed because mobile support is built into all controls.
Images
ASP.NET 2.0 has new controls for handling images:
 The ImageMap control - image map support

 The DynamicImage control - image support for different browsers
These controls are important for better image display on mobile devices, like hand-held
computers and cell phones.
Automatic Compilation
ASP.NET 2.0 provides automatic compilation. All files within a directory will be compiled on
the first run, including support for WSDL, and XSD files.
Compiled Deployment (Installation) and Source Protection

ASP.NET 2.0 also provides pre-compilation. An entire web site can be pre-compiled. This
provides an easy way to deploy (upload to a server) compiled applications, and because only
compiled files are deployed, the source code is protected.
Site Management
ASP.NET 2.0 has three new features for web site configuration and management:
 New local management console

 New programmable management functions (API)
 New web-based management tool
Development Tools
With ASP.NET Visual Studio.NET was released with project and design features targeted at
corporate developers.
With ASP.NET 2.0, Visual Studio 2005 was released.
Key design features for Visual Studio 2005 include:
 Support for the features described above

 Upload files from anywhere (FTP, File System, Front Page....)
 No project files, allowing code to be manipulated outside Visual Studio
 Integrated Web Site Administration Tool
 No "build" step - ability to compile on first run
Visual Web Developer is a new free ASP.NET 2.0 tool for non-corporate developers who don't
have access to Visual Studio.NET.
Master pages provide templates for other pages on your web site.
Master Pages
Master pages allow you to create a consistent look and behavior for all the pages (or group of
pages) in your web application.
A master page provides a template for other pages, with shared layout and functionality. The
master page defines placeholders for the content, which can be overridden by content pages. The
output result is a combination of the master page and the content page.
The content pages contains the content you want to display.
When users request the content page, ASP.NET merges the pages to produce output that
combines the layout of the master page with the content of the content page.
Master Page Example

<%@ Master %>
<html>
<body>
<h1>Standard Header For All Pages</h1>
<asp:ContentPlaceHolder id="CPH1" runat="server">
</asp:ContentPlaceHolder>
</body>
</html>
The master page above is a normal HTML page designed as a template for other pages.
The @ Master directive defines it as a master page.
The master page contains a placeholder tag <asp:ContentPlaceHolder> for individual content.
The id="CPH1" attribute identifies the placeholder, allowing many placeholders in the same
master page.
This master page was saved with the name "master1.master".
Note: The master page can also contain code, allowing dynamic content.
Content Page Example

<%@ Page MasterPageFile="master1.master" %>
<asp:Content ContentPlaceHolderId="CPH1" runat="server">

<h2>Individual Content</h2>
<p>Paragraph 1</p>
<p>Paragraph 2</p>
</asp:Content>
The content page above is one of the individual content pages of the web.
The @ Page directive defines it as a standard content page.
The content page contains a content tag <asp:Content> with a reference to the master page
(ContentPlaceHolderId="CPH1").
This content page was saved with the name "mypage1.aspx".
When the user requests this page, ASP.NET merges the content page with the master page.
Click to display mypage1.aspx.
Note: The content text must be inside the <asp:Content> tag. No content is allowed outside the
tag.
Content Page With Controls
<%@ Page MasterPageFile="master1.master" %>
<asp:Content ContentPlaceHolderId="CPH1" runat="server">

<h2>W3Schools</h2>
<asp:TextBox id="textbox1" runat="server" />
<asp:Button id="button1" runat="server" text="Button" />
</form>
</asp:Content>
The content page above demonstrates how .NET controls can be inserted into the content page
just like an into an ordinary page.
ASP.NET 2.0 has built-in navigation controls
Web Site Navigation

Maintaining the menu of a large web site is difficult and time consuming.
In ASP.NET 2.0 the menu can be stored in a file to make it easier to maintain. This file is
normally called web.sitemap, and is stored in the root directory of the web.
In addition, ASP.NET 2.0 has three new navigation controls:
 Dynamic menus
 TreeViews
 Site Map Path
The Sitemap File

The following sitemap file is used in this tutorial:
<?xml version="1.0" encoding="ISO-8859-1" ?>

<siteMap>
<siteMapNode title="Home" url="/aspnet/w3home.aspx">
<siteMapNode title="Services" url="/aspnet/w3services.aspx">
<siteMapNode title="Training" url="/aspnet/w3training.aspx"/>
<siteMapNode title="Support" url="/aspnet/w3support.aspx"/>
</siteMapNode>
</siteMapNode>
</siteMap>
Rules for creating a sitemap file:
 The XML file must contain a <siteMap> tag surrounding the content
 The <siteMap> tag can only have one <siteMapNode> child node (the "home" page)
 Each <siteMapNode> can have several child nodes (web pages)
 Each <siteMapNode> has attributes defining page title and URL
Note: The sitemap file must be placed in the root directory of the web and the URL attributes
must be relative to the root directory.
Dynamic Menu
The <asp:Menu> control displays a standard site navigation menu.
Code Example:
<asp:SiteMapDataSource id="nav1" runat="server" />
<asp:Menu runat="server" DataSourceId="nav1" />
</form>
The <asp:Menu> control in the example above is a placeholder for a server created navigation
menu.
The data source of the control is defined by the DataSourceId attribute. The id="nav1"
connects it to the <asp:SiteMapDataSource> control.
The <asp:SiteMapDataSource> control automatically connects to the default sitemap file

(web.sitemap).
Click here to see a demo of Menu, TreeView, and SiteMapPath
TreeView
The <asp:TreeView> control displays a multi level navigation menu.
The menu looks like a tree with branches that can be opened or closed with + or - symbol.
Code Example:
<asp:SiteMapDataSource id="nav1" runat="server" />
<asp:TreeView runat="server" DataSourceId="nav1" />
</form>
The <asp:TreeView> control in the example above is a placeholder for a server created
navigation menu.
The data source of the control is defined by the DataSourceId attribute. The id="nav1"
connects it to the <asp:SiteMapDataSource> control.
The <asp:SiteMapDataSource> control automatically connects to the default sitemap file

(web.sitemap).
Click here to see a demo of Menu, TreeView, and SiteMapPath
SiteMapPath
The SiteMapPath control displays the trail (navigation path) to the current page. The path acts as
clickable links to previous pages.
Unlike the TreeView and Menu control the SiteMapPath control does NOT use a
SiteMapDataSource. The SiteMapPath control uses the web.sitemap file by default.
Tips: If the SiteMapPath displays incorrectly, most likely there is an URL error (typo) in the
web.sitemap file.
Code Example:
<asp:SiteMapPath runat="server" />
</form>
The <asp:SiteMapPath> control in the example above is a placeholder for a server created site
path display.
HTML server controls are HTML tags understood by the server.

HTML Server Controls
HTML elements in ASP.NET files are, by default, treated as text. To make these elements
programmable, add a runat="server" attribute to the HTML element. This attribute indicates that
the element should be treated as a server control.
Note: All HTML server controls must be within a <form> tag with the runat="server" attribute!
Note: ASP.NET requires that all HTML elements must be properly closed and properly nested.
HTML Server Control Description

HtmlAnchor Controls an <a> HTML element
HtmlButton Controls a <button> HTML element
HtmlForm Controls a <form> HTML element
Controls other HTML element not specified by a specific HTML
HtmlGeneric
server control, like <body>, <div>, <span>, etc.
HtmlImage Controls an <image> HTML element
Controls <input type="button">, <input type="submit">, and
HtmlInputButton
<input type="reset"> HTML elements
HtmlInputCheckBox Controls an <input type="checkbox"> HTML element
HtmlInputFile Controls an <input type="file"> HTML element
HtmlInputHidden Controls an <input type="hidden"> HTML element
HtmlInputImage Controls an <input type="image"> HTML element
HtmlInputRadioButton Controls an <input type="radio"> HTML element
Controls <input type="text"> and <input type="password"> HTML
HtmlInputText
elements
HtmlSelect Controls a <select> HTML element
HtmlTable Controls a <table> HTML element
HtmlTableCell Controls <td>and <th> HTML elements
HtmlTableRow Controls a <tr> HTML element
HtmlTextArea Controls a <textarea> HTML element
Web server controls are special ASP.NET tags understood by the server.
Web Server Controls

Like HTML server controls, Web server controls are also created on the server and they require a
runat="server" attribute to work. However, Web server controls do not necessarily map to any
existing HTML elements and they may represent more complex elements.
The syntax for creating a Web server control is:
Web Server Control Description

AdRotator Displays a sequence of images
Button Displays a push button
Calendar Displays a calendar
CalendarDay A day in a calendar control
CheckBox Displays a check box
CheckBoxList Creates a multi-selection check box group
DataGrid Displays fields of a data source in a grid
DataList Displays items from a data source by using templates
DropDownList Creates a drop-down list
HyperLink Creates a hyperlink
Image Displays an image
ImageButton Displays a clickable image
Displays static content which is programmable (lets you apply
Label
styles to its content)
LinkButton Creates a hyperlink button
ListBox Creates a single- or multi-selection drop-down list
ListItem Creates an item in a list
Displays static content which is programmable(does not let you
Literal
apply styles to its content)
Panel Provides a container for other controls
PlaceHolder Reserves space for controls added by code
RadioButton Creates a radio button
RadioButtonList Creates a group of radio buttons
BulletedList Creates a list in bullet format
Repeater Displays a repeated list of items bound to the control
Style Sets the style of controls
Table Creates a table
TableCell Creates a table cell
TableRow Creates a table row
TextBox Creates a text box
Xml Displays an XML file or the results of an XSL transform
Validation server controls are used to validate user-input.

Validation Server Controls
A Validation server control is used to validate the data of an input control. If the data does not
pass validation, it will display an error message to the user.
The syntax for creating a Validation server control is:
Validation Server Control Description

Compares the value of one input control to the value of
CompareValidator
another input control or to a fixed value
Allows you to write a method to handle the validation of
CustomValidator
the value entered
Checks that the user enters a value that falls between two
RangeValidator
values
Ensures that the value of an input control matches a
RegularExpressionValidator
specified pattern
RequiredFieldValidator Makes an input control a required field
Displays a report of all validation errors occurred in a
ValidationSummary
Web page

Tutorials

Uploaded by

Tutorials

Uploaded by

What You Should Already Know

 WWW, HTML, XML and the basics of building Web pages

What is Classic ASP?

ASP 3.0 was the last version of classic ASP.

ASP.NET is NOT ASP

ASP.NET is the major part of the Microsoft's .NET Framework.

 ASP.NET is a Microsoft Technology

What is an ASP.NET File?

How Does ASP.NET Work?

The Microsoft .NET Framework

The Microsoft .NET Framework was developed to solve this problem.

.NET Frameworks keywords:

The .NET Framework consists of 3 main parts:

Server technologies and client technologies:

 ASP .NET (Active Server Pages)

 Visual Studio .NET (VS .NET)

This tutorial is about ASP.NET.

ASP.NET provides increased performance by running compiled code.

ASP.NET code is not fully backward compatible with ASP.

ASP.NET supports full Visual Basic, not VBScript.

ASP.NET supports C# (C sharp) and C++.

ASP.NET supports JScript.

Event Aware Controls

User Accounts and Roles

Server-to-server communication has been greatly enhanced, making it possible to scale an

What You Need

Or even better: start with a fresh Windows 2000 or XP installation!

Service Packs and Updates

You are now ready to develop your first ASP.NET application!

The .NET Software Development Kit

Connection Speed and Download Time

A simple ASP.NET page looks just like an ordinary HTML page.

Hello W3Schools in HTML

Hello W3Schools in ASP.NET

This code displays our example as an ASP.NET page:

How Does it Work?

Now() is a function returning the servers current date and time.

Dynamic Page in ASP .NET

Limitations in Classic ASP

ASP.NET - Server Controls

Server controls are tags that are understood by the server.

There are three kinds of server controls:

 HTML Server Controls - Traditional HTML tags

ASP.NET - Web Server Controls

<asp:control_name id="some_id" runat="server" />

ASP.NET - Validation Server Controls

By default, page validation is performed when a Button, ImageButton, or LinkButton control is

The syntax for creating a Validation server control is:

<asp:control_name id="some_id" runat="server" />

ASP.NET - Event Handlers

Note: The Page_Load event contains no object references or event arguments!

The Page.IsPostBack Property

ASP.NET Web Forms

...HTML + server controls

<form name="_ctl0" method="post" action="page.aspx" id="_ctl0">

<asp:Button id="id" text="label" OnClick="sub" runat="server" />

Maintaining the ViewState

<form name="_ctl0" method="post" action="page.aspx" id="_ctl0">

<form action="demo_classicasp.aspx" method="post">

The TextBox Control

A TextBox with text:

A TextBox with height:

A TextBox with width:

The Button control is used to display a push button.

The Button Control

The example below demonstrates a simple Button control:

Items are added to the ArrayList with the Add() method.

Data Binding to an ArrayList

The Hashtable object contains items in key/value pairs.

Try it Yourself - Examples

Items are added to the Hashtable with the Add() method.

To bind data to a RadioButtonList control, first create a RadioButtonList control

Then add the script that builds the list:

sub displayMessage(s as Object,e As EventArgs)

The SortedList Object

Then add the script that builds the list: