CHANGELOG

2.0.2 (2012-04-27)
- Added AjaxOptions property to PaginationModel, so the DisplayTemplate option can be 
  used in Ajax scenarios. Thanks to Raffaele.
- Added AlwaysAddFirstPageNumber configuration option to force the page number to be
  set for page 1.
  This is for scenarios where omitting the page parameter not automatically defaults
  to page 1.

2.0.0 (2012-04-20)
- Refactored and simplified Html.Pager helper. The number of overloads is 
  drastically reduced. Optional parameters are added via a Fluent interface.
- Introduced PaginationModel and optional DisplayTemplate for more display
  flexibility (https://github.com/martijnboland/MvcPaging/pull/6), thanks Rajeesh C V!
- Added MaxNrOfPages option (https://github.com/martijnboland/MvcPaging/pull/4)
- BREAKING CHANGE: Html.Pager overloads with actionName and routeValues have been 
  removed. Use the Options method:
  Html.Pager(pageSize, pageNumber, totalItemCount).Options(o => o.Action("ActionName"))
- BREAKING CHANGE: the Ajax.Pager helper is removed. For AJAX scenarios use the
  Html.Pager(pageSize, pageNumber, totalItemCount, ajaxOptions) overload

1.0.3 (2012-03-22)
- Added non-generic IPagedList interface for convenience.

1.0.2 (2011-12-07)
- 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).

1.0.1 (2011-08-15)
- Added fix for incorrect URL generation in some scenario's where controller
  and/or action are missing in the route values dictionary.
  Thanks to John M. Holliday for the fix.

1.0.0 (2011-05-12)
- Initial release of Pager Helper and IPagedList<T> implementation.