Application service base class for CRUD operations

What do you think about creating an application service base class or interface for CRUD operations

example:

public interface IEmployeesService : ICRUDService<EmployeeDto>
{
    public Create(EmployeeDTO employee){...}
}
...

[hikalkan]

Mini Documentation

An application service for Message entity which uses MessageDto as DTO for all methods:

public class MessageAppService : AsyncCrudAppService<Message, MessageDto>
{
    public MessageAppService(IRepository<Message> repository)
        : base(repository)
    {

    }
}

AsyncCrudAppService’s all methods are async. You can derive from CrudAppService if you prefer sync methods instead of async. MessageDto is like that:

[AutoMap(typeof(Message))]
public class MessageDto : FullAuditedEntityDto
{
    public int? TenantId { get; set; }

    public string Text { get; set; }
}

If you want to define interface for your application service:

public interface IMessageAppService : IAsyncCrudAppService<MessageDto>
{

}

Then you can implement IMessageAppService for MessageAppService without any code change.

In this sample, I used MessageDto for all methods. But we could specify CreateInput, UpdateInput, DeleteInput types and specify an input type for GetAll method (default input type is PagedAndSortedResultRequestInput, but your custom input type may not use paging/sorting). We can also override all base methods and customize mapping (which uses IObjectMapper by default).

[alexandis]

You can use https://github.com/aspnetboilerplate/aspnetboilerplate/blob/dev/src/Abp/Application/Services/AsyncCrudAppService.cs

Yes, I know 😃 but I already use CrudAppService, which is not -Async. Though, its methods are async-ready, so I want to have strong reason to rewrite my code to using AsyncCrudAppService