The GridView, DetailsView, and FormView controls all support out of the box paging support that can be enabled at the tick of a checkbox. When configured
to enable paging, these controls automatically render a paging interface comprised of LinkButtons, Buttons, or ImageButtons. The particular paging interface
configuration - whether Next/Previous links are used, whether numeric paging options are used, the text displayed in the various buttons, and so on -
are customizable through the data Web controls' properties. While these configuration options are nice, they only allow for a small amount of customization.
For instance, the configuration options let you specify if you want the paging interface to appear at the top or bottom of the control (or in both locations).
But if you want the paging interface to appear elsewhere on the page, separate from the paging interface, you're out of luck.
The ASP.NET team remedied this problem with the ListView control by decoupling paging support from the ListView control and moving it to a separate,
stand-along control, the DataPager. The DataPager control's sole purpose is to render a paging interface and communicate to its corresponding ListView
control once the user interacts with the interface (such as choosing to move to the last page of data). This explicit separation between the ListView
and DataPager allow for a much greater degree of paging interface customization and positioning, as we will se in this article.
Read on to learn more!
Read More >