Anderson Matos

Not yet, no. I had some personal issues to solve on the last couple of months. I'll review and upgrade this project on the next couple of days, though, and...

Check out [this sample project](https://github.com/ALMMa/datatables.aspnet/tree/dev/samples/DataTables.AspNet.Samples.Mvc5.AdditionalParameters) wich enables both request and response additional parameters. I'll improve this behavior for vnext. For now, you must enable additional parameters parsing on the options...

This is probably caused here: https://github.com/ALMMa/datatables.aspnet/blob/master/src/DataTables.AspNet.AspNetCore/DataTablesResponse.cs#L162 Already mapped on https://github.com/ALMMa/datatables.aspnet/issues/48 But for some quite interesting reason people tend to blame the author, fork the project and re-ship libraries instead of...

I'm currently working back on this library and this will be fixed on the next release.

Accidentally closed, sorry.

I'll keep this open to review this issue when possible. I'll try to make DataTables.AspNet work with AspNet Boilerplate without manual ajustments, if possible.

Hello, @TimeBomb006. First of all, thanks for your feedback. I've been really busy with some upgrades to AspNet5 so I couldn't answer earlier. I'm sorry to inform that there isn't...

Check out issue #47 As I've said there, this behavior is not optimal and will be improved but for now, you _must_ enable the request parameters on the DataTables.AspNet options...

Check code and comments on `Global.asax` for the additional parameters sample project. You have to explicitly set the DataTables.AspNet project to allow for additional request/response parameters, as well as provide...

Hello, @spencerflagg Yes, you are correct. The parser function is different because WebApi provides different binding mechanism. For instance, instead of a `ControllerContext`, it provides a `HttpActionContext`. You might want...