Updated 2012-04-23: Version 2.0: https://blogs.taiga.nl/martijn/2012/04/23/mvcpaging-2-0/

Updated 2011-05-12: Added NuGet package: https://blogs.taiga.nl/martijn/2011/05/12/nuget-package-for-mvc-pager/

Updated 2011-03-22: Changed download link: https://github.com/martijnboland/MvcPaging. See also https://blogs.taiga.nl/martijn/2011/03/23/mvc-pager-update-now-with-ajax-support/

Updated 2009-02-04: Upgraded source and demo to ASP.NET MVC RC1

Updated 2009-01-16: Upgraded source and demo to ASP.NET MVC Beta

Updated 2008-09-09: Source and Demo now use ASP.NET MVC preview 5

On my latest gig, we used ASP.NET MVC and it was a very pleasant experience! Very clean code, clean html output and the productivity was great (which is not very common when using a technology for the first time).

Of course, since ASP.NET MVC isn’t finished yet, it leaves something to desire. At one time we needed paging and there isn’t an out-of-the-box solution for it (yet). Some googling revealed that others had already addressed this, but to be honest, I wasn’t entirely pleased with the solutions, so I grabbed the best parts and build a generic solution out of it.

I’m in a hurry, take me to the download immediately


First, there was the PagedList<T> that Scott Guthrie already used in one of the earliest MVC demo’s and that later appeared in improved incarnations from Rob Conery and  Troy Goode. This was a nice starting point, especially because we also used LINQ To SQL as our data access layer. To provide an extra extension point, I created an IPagedList<T> interface instead of using the PagedList<T> directly.

public interface IPagedList<T> : IList<T>
    int PageCount { get; }
    int TotalItemCount { get; }
    int PageIndex { get; }
    int PageNumber { get; }
    int PageSize { get; }
    bool HasPreviousPage { get; }
    bool HasNextPage { get; }
    bool IsFirstPage { get; }
    bool IsLastPage { get; }


After choosing the IPagedList<T> implementation I started thinking about how I could create an HtmlHelper extension method that renders the page links. First, I made the mistake to couple the helper to the IPagedList<T> and it took me a little while to realize that a paging HTML helper doesn’t need anything to know about the underlying data source. It’s sole purpose is to generate a list of hyperlinks for pages and the only thing we need to know is the total amount of items, the page size and the current page. This is what the most basic HtmlHelper extension looks like:

public static string Pager(this HtmlHelper htmlHelper, int pageSize, int currentPage, int totalItemCount)

We’re assuming that the page links point to the the current controller and current action. Alternatively, it’s possible to supply a different action:

public static string Pager(this HtmlHelper htmlHelper, int pageSize, int currentPage, int totalItemCount, string actionName)

Combining the Pager html helper and IPagedList<T> in a view page (that inherits from ViewPage<IPagedList<Product>>):

<table class="grid">
            <th>Product name</th>
        <% foreach (var product in Model) { %>
                <td><%= product.Name %></td>
                <td><%= product.Category %></td>
        <% } %>
<div class="pager">
    <%= Html.Pager(Model.PageSize, Model.PageNumber, Model.TotalItemCount) %>

results in this:


You probably recognize the digg-style appearance of the pager. Thanks to the ASP.NET MVC sample application KIGG for inspiration :).

Internally, the pager uses RouteTable.Routes.GetVirtualPath() to render the url’s so the page url’s can be configured via routing to create nice looking url’s like for example ‘/Categories/Shoes/Page/1’ instead of ‘/Paging/ViewByCategory?name=Shoes&page=1’.

Advanced scenarios

Many scenarios where you want to use paging also use filtering. It’s possible to pass extra parameters to the Pager helper via a RouteValueDictionary or an anonymous type. This adds these parameters to the page links that are generated:

<div class="pager">
    <%= Html.Pager(ViewData.Model.PageSize, ViewData.Model.PageNumber, ViewData.Model.TotalItemCount, new { categoryname = ViewData["CategoryDisplayName"] } )%>


That’s it. A complete solution with demo project can be downloaded below. Feel free to leave any comments or remarks. One of the things I’m not happy about is that I failed to properly unit test the pager, but that’s for a different post.


Download the paging sample solution, incl. the demo MVC web project

Check also the AJAX version of the pager written by Daniel Iglesias: http://danieliglesiaseng.blogspot.com/2010/01/ajax-paging-with-aspnet-mvc.html.

Paging with ASP.NET MVC
Tagged on:     

4 thoughts on “Paging with ASP.NET MVC

  • August 27, 2008 at 8:40 pm

    Nicely done, Martijn. I’ll go ahead and update my blog entry to use IPagedList (implementing IList) rather than the current IPagedList and add a link to this article. Thanks! =)

  • August 27, 2008 at 9:15 pm

    Thanks 🙂

  • September 14, 2008 at 1:33 am


    I am just using your code. It is great … I made a few changes:

    1. Added a new parameter to the Pager: IDictionary htmlAttributes;

    This way HTML attributes can be used on the pager. Applied to which tag? See (2)

    2. Wrapped all tag in an unordered list (ul) where each page button is a list item … In my opinion this is better; I used:

    TagBuilder pager = new TagBuilder(“ul”);

    3. Added a “box” before the buttons saying “Page {PageNumber} of {PageCount};

    4. Hide next and previous page if PageCount <= 1 In my page I use some text like “Page … of …”, or a title for each button like “Page 1”, “Next Page”, “Previous Page” … What would be the best way to add localization to this items? Thanks, Miguel

  • Pingback:Martijn Boland » Paging demo upgraded to ASP.NET MVC Beta

Leave a Reply

Your email address will not be published. Required fields are marked *