abp-dependency-rules

Prevent ABP domain layer dependencies on infrastructure by enforcing strict layer dependency rules that ensure domain logic relies only on repository abstractions and never directly references infrastructure projects, maintaining clean separation during solution reviews and refactors.

The correct ABP layered architecture dependency directions require the Domain layer to remain independent, Application to depend on Domain, HttpApi to depend on Application, and Infrastructure to implement abstractions without leaking dependencies into domain logic.

Validate project references when adding new dependencies in an ABP solution by checking the layered dependency direction table to ensure new references do not violate cross-layer rules, specifically preventing infrastructure dependencies in the domain layer.

Yes, you can use repository abstractions to decouple domain logic from infrastructure in ABP by defining repository interfaces in the domain layer and implementing them in the infrastructure layer, ensuring domain independence.

Your ABP application layer has cross-layer dependency violations during refactoring because explicit dependency directions between Domain, Application, HttpApi, and Infrastructure projects were not enforced, allowing incorrect project references to bypass clean separation guardrails.