Today, a new version of the MvcPaging library was released. The only new feature in this release is the option to add strongly typed route values. In the past you had to add extra route values for the page links
MvcPaging 2.0
Last week, a new version of the MvcPaging library has been released. This time there are some breaking changes and that’s why the major version number is increased. What’s new: Simplified API with reduced number of Html.Pager overloads; DisplayTemplate option
MvcPaging 1.0.2
A new version of the MvcPaging component is available via NuGet with the following changes: Added ItemStart and ItemEnd properties to IPagedList (Displaying items {ItemStart} – {ItemEnd}). Non-canonical url’s for page 1 (https://github.com/martijnboland/MvcPaging/issues/2). So the core library hasn’t changed much,
NuGet package for MVC pager
It’s now possible to add the MVC pager to your own project with NuGet. Or from Visual Studio with ‘Manage NuGet Packages…’ and then search for ‘MvcPaging’. After installing, you can immediately use the Pager HtmlHelper in your views: et
MVC Pager update: now with AJAX support
The MVC pager now has support for AJAX scenario’s, thanks to Bart Lenaerts. This was my first GitHub pull request and everything went pretty smoothly. Check out the demo application for an example. Visit the GitHub project page to download