scrutor
Register services using assembly scanning and a fluent API.
Total Downloads
298.7M
298,736,637
Published
Jan 28, 2022
Latest stable version
Install
.NET CLI
dotnet add package scrutor --version 4.0.0
Package Manager Console
Install-Package scrutor -Version 4.0.0
PackageReference
<PackageReference Include="scrutor" Version="4.0.0" />
Frameworks
Dependencies
Microsoft.Extensions.DependencyInjection.Abstractions
[2.1.1, )
.NETFramework4.6.1
Microsoft.Extensions.DependencyModel
[2.1.0, )
.NETFramework4.6.1
Microsoft.Extensions.DependencyInjection.Abstractions
[3.1.9, )
.NETCoreApp3.1
Microsoft.Extensions.DependencyModel
[3.1.6, )
.NETCoreApp3.1
[6.0.0, )
[6.0.0, )
Microsoft.Extensions.DependencyInjection.Abstractions
[2.1.1, )
.NETStandard2.0
Microsoft.Extensions.DependencyModel
[2.1.0, )
.NETStandard2.0
Adoption guide
Teams staying on built-in DI while reducing manual registration boilerplate.
Why it appears in the guide: Extends Microsoft DI with assembly scanning and decorator registration helpers. Trade-off: Convention-based scanning should be constrained to avoid accidental or ambiguous registrations.
Compatibility metadata lists 4 target frameworks; confirm the exact target used by your application.
How to read this guidance
Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.
Useful next steps
Move from package metadata to a concrete selection or review workflow.