More than 15 months later, we now undergo a full rewrite with support for Mvc, WebApi and AspNet (core CLR included!).
Also, unit-testing is a priority to avoid breaking your app. `Beta2` release now ships with updated support for Asp.Net 5 RC1 Update1, along with all the goodies from `Beta1`. This is the second beta release for `DataTables.AspNet`. A full migration path (for all, including MVC 5 and WebApi) will be released as soon as Asp.Net 5 becomes stable enough to stop changing namespaces (before that, it would require multiple migration paths and paths from previous paths and so on). - [DataTables.AspNet.Mvc5](https://www.nuget.org/packages/DataTables.AspNet.Mvc5/), with support for Mvc5, registration and automatic binders - [DataTables.AspNet.WebApi2](https://www.nuget.org/packages/DataTables.AspNet.WebApi2/) with support for WebApi2, registration and automatic binders - [DataTables.AspNet.AspNet5](https://www.nuget.org/packages/DataTables.AspNet.AspNet5/) with support for AspNet5, dependency injection and automatic binders
You can extend DataTables.AspNet easier through DataTables.AspNet.Core, which contains core elements including standard interfaces and enums.
Samples are provided on the `samples` folder.You can also check our wiki (TODO - Wiki) for guidance. Check a full migration path from older versions of `DataTables.AspNet` up to the most recent one.
`Beta1` also delivered some breaking changes so if you're running alpha code, check the second migration path bellow:
- Migration path from legacy DataTables.Mvc (TODO - Wiki)
- Migration path from alpha releases (TODO - Wiki)
We're still on beta so there is no stable code/release on `master` branch yet.
As soon as we're stable, `master` branch will be populated, tagging will get in place and and Nuget packages will drop the `-Pre` argument. If you can, drop it!
Beta1 is just as stable as legacy DataTables.Mvc and if you find any bug you can easily submit and get it fixed ASAP. I has been a nightmare to make tests run properly. Since beta2 I simply can't make them run correctly so I'll rely on updated sample projects to make sure everything works fine and will rewrite tests and try to make them run again.