.NET/C# dependency injection service registration Scrutor tool

Little scum · Posted on 2025-9-4 09:37:00

Requirements: When the project is relatively large and the writing syntax is very standardized, when we add an interface, we need to manually add it in the IServiceCollection container, so that the interface can be injected into the constructor. The Scrutor tool is very convenient for us to add automatically according to our rule configuration.

Scrutor

Microsoft.Extensions.DependencyInjection for assembly scanning and decorating extensions.

Source code address:The hyperlink login is visible.

review

Looking back at the service registration, the three ways of singleton injection are as follows:

Login is visible.

Service registration

Let's say you have a code structure like this:

Interface definitions
public interface IUserService { }
public interface IOrderService { }

Implementation class
public class UserService : IUserService { }
public class OrderService : IOrderService { }

before

Registration is required one by one, and the code is as follows:

Login is visible.

Or write your own method and register it through reflection (In fact, Scrutor is also through reflection), as follows:

Login is visible.

afterwards

Scrutor makes it very convenient to register assemblies scan, especially for automatically registering multiple service classes (e.g., UserService registered as IUserService). The package dependencies are as follows:

Login is visible.

The code is as follows:

Login is visible.

Interpretation:

. FromAssemblyOf<UserService>(): Specifies the assembly to scan.
. AddClasses(): Scans all classes in the assembly set.
. AsImplementedInterfaces(): Automatically registers interfaces for these classes as they are implemented.
. WithScopedLifetime(): Set the lifetime to Scoped, which can also be WithTransientLifetime() or WithSingletonLifetime().

(End)

[Tips] .NET/C# dependency injection service registration Scrutor tool

Related Posts

Sections viewed