Instead of having to add manually all services, convert this to AddCrud and AddCrudDto

Check if this is possible to have a middleware configured instead of injection:
http://www.blinkingcaret.com/2017/09/13/create-your-own-asp-net-core-middleware/

Even in the same application, I can have a resource pointing to a context/repo and another resource pointing to another context/repo.

Is it possible to support?
Test and maybe new development to do...

After giving it a try, this is not a good idea of maintaining two repositories, one for libs and one for samples. It could be easily placed at the same place within LSG.GenericCrud/LSG.GenericCrud.Samples folder for example.

This is possible to have partial crud (get entities but no create or delete for example). This should be configurable.

To be as lightweight as possible, extract everything related to automapper in its own dedicated library. In the case in a user would like only the core set of features and not the features related to DTO

Update docs and samples accordingly

Remove all business logic from repositories to strip down repositories and split logic in another service layer

Actually, we are not able to easily create custom layers on top of existing logic. Let's say I have a particular thing to do before calling the repository in the service layer and I need to make a call to a webservice.

I would need a way of creating a custom service layer on top of the actual CrudService, ie.:

public class MyCustomService : CrudService<Account> {
// default constructor
public override GetAll...{
// my custom code
base.GetAll()...

Check if there is a way of generalizing the datafillers to be compatible with IEntity instead of BaseEntity

Is this possible to get support for odata query structure. OData seems really powerful, but it seems to be tightly coupled to controllers (no middle layer or repository layer seems possible).

Steps to reproduce

1. Create or update existing entity with null value in a property
2. Try to update, BUG

Expected behavior

Should be able to update from null to SOME_VALUE in a property.

If you forget in entity/dto constructor to initialize the Id, the historical DAL has an empty Guid in entity id

There is no code that supports history for <TDto, TEntity> Crud controller

This library will be awesome with dynamic paging feature. When needed, a controller should be able to specify to enable paging and all the rest should come automatically. No additional code needed!

For historical purpose, multiple entities of multiple types needs to be created at the same time Unit of work. But, actual setup requires to use one repository per entity type which is not useful to make single commits to database.

This is a big one but being able to automatically filter data on multitenancy configuration or row and/or table security will be awesome!