Asp.Net Core 2.1 Web Api BaseCrudController

Asp.Net Core 2.1 Web Api BaseCrudController I will supply you a layered project with web api, service, business, entity, and data access layers, using Entity Framework Core 2.1. It also has a BaseCrudController. What I need is that you take my project as example, remove everything unnecessary, and only keep the required functionalities to use on any custom Entity (with sub entities). I also want you to take my BaseCrudController and adapt it to be used on any derived entity, as this one misses Guid id for update, get and delete. The needed operations are: list, get, create, update, delete, count. I also want you to implement a structure which can be used in webapi, and passed up to the repository layer, to: - order by ascending and descending. The order by should be able to have 1 or more fields, each one specifying ascending or descending - paginate by specifying page size and start element - filters based on any element of the DTO related to the Entity, which van have sub DTOs and thus sub Entities as well. The filter shpuld be able to work on 1 or more fields. This should work like a where clause on the database, and be received on the webapi actions, but be propagated through all layers up to the repository, which then performs the filters, pagination, and order by on the database and thus not on data retrieved in memory. This whole solution should be named generically, so that real web apis only specify the real names and structures of the Entity, DTO, and webapi action names. Thus i dont want to take this project and need to rename all these elements to make it work. I only want to derive, and specify the names and it should work. To proof that the solution works appropriately, please create an Order and dependant OrderItems. The structure of them you may decide for yourself. So you implement the whole solution from BaseCrudController which already need to be able to work through all layers. Then you derive OrderController from it and pass the OrderDTO with OrderItemDTO inside it, you pass OrderEntity and embedded OrderItemEntity, and the resulting webapi should work on Orders with depending OrderItems. OrderDTO, OrderItemDTO, OrderEntity, and OrderItemEntity you declare in the respective layers. Test it with both order by directions on several fields (on Order but also only on OrderItem), and on 1 and on multiple fields. Do pagination of several sizes, from the beginning, on some start positions, and near to the end. And perform filtering on several fields (on only Order and on only OrderItem). Test all the crud operations to make sure everything works as expected. All tests should be done with NUnit. Replace Ninject DI with Autofac DI as well. Do not keep any Ninject nor Microsoft DI in the whole solution, only Ninject. Seed the Order and OrderItems with at least 2000 Orders and 0, 1, 2, 3, 5, or 20 dependant items on each. Deliverables: Visual Studio 2017 solution with: - DotNet Core 2.1 webapi project for the BaseCrudController - DotNet Core 2.1 webapi project for the derived Order + OrderItem - The existing but rewritten layers: Service, Business, Entity, Data Access - NUnit test project (DotNet Core 2.1) This solution should be delivered in up to 5 days. BUDGET: USD 50 max