Assembly: System.Web.Extensions (in System.Web.Extensions.dll)
[ToolboxBitmapAttribute(typeof(DataPager), L"DataPager.ico")] [ThemeableAttribute(true)] [AspNetHostingPermissionAttribute(SecurityAction::LinkDemand, Level = AspNetHostingPermissionLevel::Minimal)] [AspNetHostingPermissionAttribute(SecurityAction::InheritanceDemand, Level = AspNetHostingPermissionLevel::Minimal)] public ref class DataPager : public Control, IAttributeAccessor, INamingContainer, ICompositeControlDesignerAccessor
The class is used to page data and to display navigation controls for data-bound controls that implement the IPageableItemContainer interface. (An example of a control that implements the interface is the ListView control.)
You can associate the control with the data-bound control by using the PagedControlID property. Alternatively, you can put the control inside the data-bound control hierarchy. For example, in the ListView control, you can put the control inside the ListView::LayoutTemplate template.
You can customize the number of items that are displayed for each page of data by changing the PageSize property. You can also change the way a page is submitted to the server by setting the QueryStringField property.
In order for the control to display navigation controls, you must add pager fields to the control. The pager fields derive from the DataPagerField class. The following table lists the pager field types that you can use.
Pager field type
Enables users to navigate through pages one page at a time, or to jump to the first or last page.
Enables users to select a page by page number.
Enables you to create a custom paging UI.
To declaratively add pager fields to the control, add a Fields element to the control. You can then add the pager fields to the Fields element. The pager fields are added to the Fields collection in the order that they appear in the Fields element. The Fields collection enables you to programmatically manage the pager fields in the control.
The following table lists read-only properties of the control that specify characteristics of the page of data. These properties are usually used for binding expressions in the TemplatePagerField object.
The default markup that is rendered default for this control might not comply with accessibility standards, such as the Web Content Accessibility Guidelines 1.0 (WCAG) priority 1 guidelines. For details about accessibility support for this control, see ASP.NET Controls and Accessibility.
|Walkthrough: Displaying, Paging, and Sorting Data Using the ListView Web Server Control||Building ASP .NET Web Applications in Visual Studio|
|Walkthrough: Displaying, Paging, and Sorting Data Using the ListView Web Server Control|
Windows 7, Windows Vista, Windows XP SP2, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003
The .NET Framework and .NET Compact Framework do not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.