Update: ASP.NET Core 2.1 and webpack 4 are released. I’ve written a new post, Lean ASP.NET Core 2.1 – manually setup a Razor Pages project with Bootstrap, NPM and webpack. A while ago I wrote about building an ASP.NET Core MVC
MvcPaging 2.1
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,
Custom Model Binders and Request Validation
In ASP.NET MVC you can create your own model binders to control the way that models are constructed from an HTTP request. For example, if you don’t want any whitespace characters in your model, you can create a custom model