ABP Dependency Injection Skill

ABP Framework dependency injection conventionally registers services by implementing marker interfaces like ITransientDependency, ISingletonDependency, or IScopedDependency. It resolves dependencies automatically without manual service wiring code.

To override an existing service registration in ABP, apply the [Dependency] attribute with the ReplaceServices option. This safely swaps the default framework implementation with your custom service while preserving the original dependency injection lifecycle.

You need Autofac for ABP dependency injection when your services require dynamic proxying for cross-cutting concerns like Unit of Work, validation, authorization, auditing, and feature checking. The default Microsoft DI container does not support these interception mechanisms.

To control which interfaces are exposed for dependency injection in ABP, apply the [ExposeServices] attribute to your service class. This restricts the injectable interfaces, ensuring only explicitly specified contracts are registered and resolvable by the DI container.

ABP dependency lifetimes define instance scope: ITransientDependency creates a new instance per injection, IScopedDependency shares instances within a single request, and ISingletonDependency maintains a single application-wide instance for caching or global state management.

Yes, you can use the [Dependency] attribute to set service lifetime in ABP alongside configuring TryRegister and ReplaceServices. This provides explicit control over the dependency injection behavior, overriding conventional interface-based registrations.