Why SOLID principles are still the foundation for modern software architecture - Stack Overflow Blog 

PM>Install-Package DNTFrameworkCore
PM>Install-Package DNTFrameworkCore.EntityFramework
PM>Install-Package DNTFrameworkCore.Web
PM>Install-Package DNTFrameworkCore.Web.EntityFramework

[Route("api/[controller]")]
public class
    TasksController : CrudController<ITaskService, int, TaskReadModel, TaskModel, TaskFilteredPagedQueryModel>
{
    public TasksController(ITaskService service) : base(service)
    {
    }

    protected override string CreatePermissionName => PermissionNames.Tasks_Create;
    protected override string EditPermissionName => PermissionNames.Tasks_Edit;
    protected override string ViewPermissionName => PermissionNames.Tasks_View;
    protected override string DeletePermissionName => PermissionNames.Tasks_Delete;
}

Revisiting SOLID principles  

In this episode, Robert is joined by Phil Japikse for a chat about design patterns. Software design patterns have been around long before the MVC Framework gained momentum. Phil starts with a review of Robert C. Martin's (Uncle Bob) SOLID macronym. After building the proper foundation,he reviews several design patterns, their C# implementation and when and how they should be used in modern software development. 

SOLID Design Patterns 

A class should have only one reason to change.

Applying S.O.L.I.D. Principles in Microsoft .NET/C#