The GridView control. This control lets you display the data from a data source in the rows and columns of a table. It includes many advanced features, such as automatic paging and sorting. It lets you update and delete data with minimal C# code. And its appearance is fully customizable.
The GridView control displays data provided by a data source in a row and column format. In fact, the GridView control renders its data as an HTML table with one Tr element for each row in the data source, and one Td element for each column in the data source.

The GridView control uses several different types of child elements to create and format its fields. The first element listed here is the Columns element, which defines the collection of columns that are displayed by the control. This element should be placed between the start and end tags for the GridView control. 

Paging refers to the ability of the GridView control to display bound data one page at a time, along with paging controls that let the user select which page of data to display next. The GridView control lets you enable paging simply by setting the AllowPaging attribute to True.
When you enable paging, an additional row is displayed at the bottom of the GridView control to display the paging controls.
paging works only for data sources that are in DataSet mode.

When you think about important parts of a navigation system, the first thing that you may come up with is a menu. Menus come in all sorts and sizes, ranging from simple and static HTML links to complex, fold-out menus driven by CSS or JavaScript. But there is more to navigation than menus alone. ASP.NET comes with a number of useful navigation controls that enable you to set up a navigation system in no time. These controls include the Menu, TreeView, and SiteMapPath.
Besides visual controls like Menu, navigation is also about structure. A well-organized site is easy for your users to navigate. The Web.sitemap file that is used by the navigation controls helps you define the logical structure of your site.

To make it easy to show relevant pages in your site using a Menu, a TreeView, or a SiteMapPath, ASP.NET uses an XML-based file that describes the logical structure of your web site. By default, this file is called Web.sitemap. This file is then used by the navigation controls in your site to present relevant links in an organized way. Simply by hooking up one of the navigation controls to the Web.sitemap file you can create complex user interface elements like fold-out menus or a tree view.

ADO.NET is the new database technology of the .NET (Dot Net) platform, and it builds on Microsoft ActiveX® Data Objects (ADO). ADO is a language-neutral object model that is the keystone of Microsofts Universal Data Access strategy. ADO.NET is an integral part of the .NET Compact Framework, providing access to relational data, XML documents, and application data. ADO.NET supports a variety of development needs. You can create database-client applications and middle-tier business objects used by applications, tools, languages or Internet browsers.

If you execute a command that contains a Select statement, the result is a result set that contains the rows you requested. To read through the rows in the result set, you use a data reader object. Although a data reader provides an efficient way of reading the rows in a result set, you can‟t use it to modify those rows. In addition, it only lets you read rows in a forward direction. Once you read the next row, the previous row is unavailable. Because of that, you typically use a data reader to retrieve and work with a single database row at a time.

LINQ enables you to query data from a wide variety of data sources, directly from your programming code. LINQ is to .NET programming what SQL is to relational databases. With straightforward, declarative syntax you can query collections for objects that match your criteria. LINQ is not just an add-on that is part of the .NET Framework. On the contrary, LINQ has been designed and implemented as a true part of the programming languages in .NET. This means that LINQ is truly integrated into .NET, giving you a unified way to query data, regardless of where that data comes from. In addition, because it is integrated into the language and not in a certain project type, LINQ is available in all kinds of projects including web applications, Windows Forms applications, Console applications, and so on. To help developers get familiar with LINQ, its syntax is closely modeled after SQL, the most popular query language for relational databases. This means that LINQ has keywords such as Select, From, and Where to get data from a data source. 

ASP.NET 3.5 Framework includes the following five List controls:

Controls Description
Bullet List A bulleted list of items.
Each item can be displayed as text, a link button, or a hyperlink.
CheckBox List A list of check boxes.
Multiple check boxes in the list can be selected.
DropDown List A drop-down list.
Only one item in the drop-down list can be selected.
ListBox A list box.
Only one item in the list can be selected or multiple items can be selected.
RadioButtonList A list of radio buttons.
Only one radio button can be selected.

ASP.Net solves this problem by creating a unique cookie for each user. The cookie is sent to the users computer and it contains information that identifies the user. This interface is called the Session object. The Session object stores information about, or change settings for a user session. Variables stored in a Session object hold information about one single user, and are available to all pages in one application. Common information stored in session variables are name, id, and preferences. The server creates a new Session object for each new user, and destroys the Session object when the session expires.

A session starts when:

  • A new user requests an ASP file, and the Global.asa file includes a Session_OnStart procedure
  • A value is stored in a Session variable
  • A user requests an ASP file, and the Global.asa file uses the <object> tag to instantiate an object with session scope

A session ends if a user has not requested or refreshed a page in the application for a specified period. By default, this is 20 minutes.If you want to set a timeout interval that is shorter or longer than the default, use the Timeout property.The example below sets a timeout interval of 5 minutes:
<% Session.Timeout=5 %>

PreviousDisplaying 6 of 7Next
1 2 3 4 5 6 7
Need Help? Contact Us.

Log in


Forgot password?


New User