How deeply does ASP.NET Core in Action, 3e cover SOLID principles?

Defines the five-principle mnemonic and connects it to dependency injection, but does not explain each principle individually.

SOLID principles

As explained in ASP.NET Core in Action, 3e

SOLID is a mnemonic for five object-oriented design principles: single responsibility, open-closed, Liskov substitution, interface segregation, and dependency inversion.

SOLID is a mnemonic for five object-oriented design principles: single responsibility, open-closed, Liskov substitution, interface segregation, and dependency inversion. section 8.1

These principles provide durable guidance for object-oriented software design. ASP.NET Core applies dependency injection throughout its framework libraries, connecting SOLID with modular application structure. section 8.1

Registration email service

A registration handler can construct EmailSender and all its dependencies manually, but dependency injection lets the handler request EmailSender while the container supplies its dependencies. This illustrates the practical relationship between dependency inversion and dependency injection. section 8.1

How ASP.NET Core in Action, 3e covers it

liveBook manning.com

Read ASP.NET Core in Action, 3e on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

AI-Powered Developer: Build software with ChatGPT and CopilotA set of five software-design principles intended to improve the flexibility and maintainability of object-oriented designs.
liveBook manning.com

Functional Design and Architecture: Examples in HaskellSOLID is a set of five object-oriented design principles concerning responsibility, extensibility, substitutability, interface design, and dependency management.

Compare how 3 books explain SOLID principles →

Related concepts

Liskov Substitution Principlehas part · The Liskov Substitution Principle is a software design principle requiring objects of a subtype to be usable wherever objects of its supertype are expected without violating behavioral expectations or program correctness.
single responsibility principleincludes · The single responsibility principle is a software design principle that gives a component one focused responsibility and one primary reason to change.
open-closed principleincludes · The open-closed principle is a software design principle that software entities should be open to extension but closed to modification.
wasteaddresses · Waste is activity or resource consumption that does not contribute useful value to an intended product, process, customer, or organizational outcome.
Interface Segregation Principleincludes · The Interface Segregation Principle favors focused interfaces so clients and implementations depend only on operations they require.
dependency inversionincludes · Dependency inversion is a design principle in which high-level policy and low-level implementation depend on abstractions rather than directly on each other.

This explainer was generated by Manning's knowledge graph from the text of ASP.NET Core in Action, 3e. The section links point to the parts of the book it draws on.