abp-dependency-rules

Valid cross-layer references in an ABP framework project dictate that layers like Domain and Application.Contracts can be referenced by higher layers, ensuring strict domain and infrastructure separation. The rules detail exact allowed dependencies to maintain architectural consistency.

To prevent domain logic from depending on infrastructure in ABP, apply the project dependency rules to audit your code structure. The rules highlight common architectural violations, ensuring your domain layer remains isolated and relies only on abstractions.

Yes, you can use ABP dependency rules for code reviews and architectural consistency checks. The rules provide a checklist for structuring code across Domain.Shared, Application, and Infrastructure layers to enforce domain driven design constraints.

When adding features to an ABP project, place new service implementations in the correct layer by following the ABP dependency rules. This ensures the service references only necessary abstractions and maintains proper project layer separation.

The correct project layer structure for domain driven design in ABP involves Domain.Shared, Domain, Application.Contracts, Application, and Infrastructure layers. The dependency rules define how these layers interact to enforce repository pattern usage and clean architecture.

Your ABP application layer fails architectural consistency checks when it directly references implementations instead of abstractions. The ABP dependency rules identify these common violations, preventing application layers from breaking domain and infrastructure separation.