DotThrow.DependencyInjection 2.0.2

.NET 8.0 This package targets .NET 8.0. The package is compatible with this framework or higher. .NET Standard 2.0 This package targets .NET Standard 2.0. The package is compatible with this framework or higher. .NET Framework 4.6.2 This package targets .NET Framework 4.6.2. The package is compatible with this framework or higher. 
dotnet add package DotThrow.DependencyInjection --version 2.0.2
                    


                    

                
NuGet\Install-Package DotThrow.DependencyInjection -Version 2.0.2
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="DotThrow.DependencyInjection" Version="2.0.2" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="DotThrow.DependencyInjection" Version="2.0.2" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="DotThrow.DependencyInjection" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add DotThrow.DependencyInjection --version 2.0.2
                    


                    

                
#r "nuget: DotThrow.DependencyInjection, 2.0.2"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package DotThrow.DependencyInjection@2.0.2
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=DotThrow.DependencyInjection&version=2.0.2
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=DotThrow.DependencyInjection&version=2.0.2
                    


                            Install as a Cake Tool

DotThrow.DependencyInjection

Microsoft.Extensions.DependencyInjection support for DotThrow validators:

  • Register validators by assembly scanning, with the same methods as FluentValidation.
  • Register one validator at a time without reflection (trimming and Native AOT safe).
  • Validate options classes with a DotThrow validator, with ValidateOnStart and named options.
  • Register dynamic validators whose rules live in appsettings.json (or any IConfiguration) and reload when the configuration changes.

Targets netstandard2.0, .NET Framework 4.6.2, .NET 8, .NET 9 and .NET 10. It depends on DotThrow, Microsoft.Extensions.Configuration.Abstractions, Microsoft.Extensions.DependencyInjection.Abstractions, Microsoft.Extensions.Logging.Abstractions and Microsoft.Extensions.Options.

Install

dotnet add package DotThrow.DependencyInjection

Packages

The DotThrow packages share one version:

  • DotThrow: guard clauses, collect mode, Validator<T>, dynamic rules, message translations and analyzers. No dependencies.
  • DotThrow.DependencyInjection (this package): register validators in dependency injection, validate options classes, and dynamic validators from configuration.
  • DotThrow.AspNetCore: validation for minimal API endpoints and MVC actions, and validation problem helpers.

Register validators

using Microsoft.Extensions.DependencyInjection;

// Every public validator class in the assembly, scoped (one per request in web apps).
services.AddValidatorsFromAssemblyContaining<Program>();

// The same, with a lifetime, a filter and internal classes.
services.AddValidatorsFromAssembly(
    typeof(Program).Assembly,
    ServiceLifetime.Singleton,
    filter: result => result.ValidatorType != typeof(LegacyValidator),
    includeInternalTypes: true);

// No scanning: safe for trimming and Native AOT.
services.AddValidator<SignUp, SignUpValidator>();
services.AddValidator(new Validator<Contact>()
    .For(x => x.Email, email => email.IfNullOrWhiteSpace().IfNotEmailAddress()));
services.AddValidator(sp => new OrderValidator(sp.GetRequiredService<IStockService>()));

Each validator class is registered the same way FluentValidation does it: as every IValidator<T> it implements and as the class itself. Then ask for IValidator<SignUp> in a constructor or a minimal API handler.

When several classes validate the same model, all of them are registered, so IEnumerable<IValidator<T>> gets every one. A single IValidator<T> resolves to the last one registered. Scanning registers in a fixed order: a class after its base classes, then by full type name. So StrictOrderValidator : OrderValidator wins over OrderValidator, but between two unrelated validators the winner only depends on their names. Keep one validator per model, or leave the others out with the scanning filter.

Types that cannot be loaded (an assembly they need is missing) are skipped, so AddValidatorsFromAssemblies(AppDomain.CurrentDomain.GetAssemblies()) works.

Assembly scanning uses reflection and is marked [RequiresUnreferencedCode]. In trimmed and Native AOT apps use AddValidator.

Validate options

public sealed class SmtpOptions
{
    public string? Host { get; set; }

    public int Port { get; set; }
}

public sealed class SmtpOptionsValidator : Validator<SmtpOptions>
{
    public SmtpOptionsValidator()
    {
        For(x => x.Host, host => host.IfNullOrWhiteSpace());
        For(x => x.Port, port => port.IfOutOfRange(1, 65535));
    }
}

builder.Services.AddValidator<SmtpOptions, SmtpOptionsValidator>();
builder.Services.AddOptions<SmtpOptions>()
    .BindConfiguration("Smtp")
    .ValidateWithDotThrow()
    .ValidateOnStart();

With "Port": 0 in the configuration the app does not start:

Microsoft.Extensions.Options.OptionsValidationException: SmtpOptions.Port: 'Port' must be between 1 and 65535.

Other forms:

// A validator object.
services.AddOptions<SmtpOptions>().ValidateWithDotThrow(new SmtpOptionsValidator());

// Rules written inline.
services.AddOptions<SmtpOptions>("backup")
    .BindConfiguration("BackupSmtp")
    .ValidateWithDotThrow(v => v.For(x => x.Port, port => port.IfOutOfRange(1, 65535)));
  • Each failure becomes one message, named by its property path (SmtpOptions.Credentials.UserName).
  • Named options are validated by name. Reloaded configuration is validated again.
  • The registered validator may have any lifetime: it is resolved in its own scope.
  • Options validation is synchronous, so the validator must not have async rules (MustAsync, CustomAsync); such a validator throws AsyncRuleInvokedSynchronouslyException.

Dynamic rules from configuration

Rules can live in configuration instead of code, in the shape of RuleSetDefinition (see the dynamic rules guide):

{
  "Validation": {
    "SignUp": {
      "rules": [
        { "property": "Email", "checks": [ "WhiteSpace", "NotEmailAddress" ] },
        { "property": "Age", "severity": "Warning", "checks": [ { "check": "OutOfRange", "min": 18, "max": 130 } ] }
      ]
    }
  }
}

// Reflection finds the properties.
builder.Services.AddDynamicValidator<SignUp>(builder.Configuration.GetSection("Validation:SignUp"));

// Trimming and Native AOT: name the properties the rules may check.
builder.Services.AddDynamicValidator(
    "Validation:SignUp",
    new PropertyMap<SignUp>().Add(x => x.Email).Add(x => x.Age),
    o =>
    {
        o.Checks = new CheckRegistry().Add<string>("NotReserved", (email, _) => email.IfOneOf("admin@example.com"));
        o.CodeRules = v => v.For(x => x.Password, p => p.IfNullOrEmpty().IfShorterThan(12));
        o.OnReloadError = (error, services) => services.GetRequiredService<RulesHealth>().Failed(error.Errors);
    });
  • The validator is a singleton IValidator<T> and DynamicValidator<T>. One per type: a second call for the same type replaces the first.
  • When the section changes (for example reloadOnChange: true on a JSON file), the rules are read again and swapped in one step. Changes to other sections, or saving the same values again, do nothing. Rules with errors are not used: the old rules stay, the failure is logged as an error through ILogger<DynamicValidator<T>>, and OnReloadError (if set) gets every error. Without logging and without OnReloadError, the failure goes to Trace.TraceError.
  • A definition with errors fails when the validator is first resolved, and also when the host starts (ValidateOnStart, on by default), with every error and its place, for example Rules[0].Checks[1].Chek (Validation:SignUp:rules:0:checks:1:chek): unknown key (did you mean 'check'?).
  • AddDynamicValidator<T>(RuleSetDefinition) registers rules from code, a database or RuleSetDefinition.FromJson; change them with DynamicValidator<T>.Update.
  • The section is read without the configuration binder (RuleSetConfiguration.Read), so the PropertyMap overloads are safe for trimming and Native AOT. Configuration stores a JSON null as an empty string, so empty values read as not set.

Moving from FluentValidation

AddValidatorsFromAssembly, AddValidatorsFromAssemblies and AddValidatorsFromAssemblyContaining take the same arguments. The filter gets a DotThrow.Scanning.AssemblyScanResult with InterfaceType, ValidatorType and ModelType. One difference: a class that implements several IValidator<T> interfaces is registered for all of them (FluentValidation registers the first).

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 is compatible.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 is compatible.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
2.0.2 91 10/11/2026
2.0.1 94 10/10/2026
2.0.0 89 10/10/2026
2.0.0-rc.1 55 10/10/2026

https://github.com/shanto462/DotThrow/blob/main/CHANGELOG.md