.NET news » ASP.NET 
A Crash Course on ASP.NET Control Development: Template Properties
DayPilot - Building an Outlook-Like Calendar Component for ASP.NET
New version of AspLib component library
Secure File Download using Basic Authentication
Top 10 Annotations and Remarks about the Wonderful and Powerful New Features in ASP.NET 2.0
A comparison between ASP.NET 1.x and ASP.NET 2.0
Search Engine Optimization (SEO) and ASP.NET Developers
Switching Between HTTP and HTTPS Automatically: Version 2
Custom Paging in ASP.NET 2.0 with SQL Server 2005
AllowPaging property to True and add a few lines of code in the PageIndexChanged
event handler and you were done! ASP.NET 2.0's
GridView makes
the process even simpler - just check the Enable Paging option from the GridView's smart tag - no code needed.
Of course nothing is free in life, and the tradeoff you make with the ease of checking a checkbox to enable paging (or, in the DataGrid's case, writing a couple lines of code) is performance. Out of the box, the DataGrid and GridView use default paging, which is a simple paging model that returns all of the records for each every page of data shown. When paging through small amounts of data (dozens to a hundred or so records), this inefficiency is likely outweighed by the ease of adding the feature. However, if you want to page through thousands, tens of thousands, or hundreds of thousands of records the default paging model is not viable.
The alternative to default paging is custom paging, in which you are tasked with writing code that intelligently grabs the correct subset of data. It requires a bit more work, but is essential when dealing with sufficiently-sized data...


