在Fluent Validation中编写模型验证器时，如何访问其他模型的属性？

下面针对你遇到的场景，提供几种实用的实现方式：

1. 给Person模型添加Department导航属性（最简单的关联场景） #

如果Person和Department本来就有数据库外键关联，直接在Person类中添加Department的导航属性，验证时就能直接拿到对应的部门数据：

// Person.cs
public class Person
{
    public decimal Salary { get; set; }
    public int DepartmentId { get; set; } // 关联部门的外键
    public Department Department { get; set; } // 导航属性，EF Core会自动加载关联数据
}

// 自定义薪资验证属性
public class SalaryLimitAttribute : ValidationAttribute
{
    protected override ValidationResult IsValid(object value, ValidationContext validationContext)
    {
        var person = validationContext.ObjectInstance as Person;
        if (person?.Department == null)
        {
            return new ValidationResult("无法获取部门配置信息");
        }

        var inputSalary = (decimal)value;
        // 直接访问Department的属性，比如MaxAllowedSalary
        if (inputSalary > person.Department.MaxAllowedSalary)
        {
            return new ValidationResult($"该部门最高薪资上限为{person.Department.MaxAllowedSalary}，当前薪资超出限制");
        }

        return ValidationResult.Success;
    }
}

然后在Person的Salary属性上标记该特性：

[SalaryLimit]
public decimal Salary { get; set; }

2. 通过依赖注入获取Department仓储（动态查询场景） #

如果Person模型没有直接关联Department，或者需要实时从数据库拉取最新的部门配置，可以在验证器中注入部门仓储来查询数据：

// 定义部门仓储接口
public interface IDepartmentRepository
{
    Department GetById(int departmentId);
    Task<Department> GetByIdAsync(int departmentId, CancellationToken cancellationToken);
}

// 支持依赖注入的自定义验证属性
public class SalaryLimitAttribute : ValidationAttribute, IValidatableObject
{
    private readonly IDepartmentRepository _departmentRepo;

    // 构造函数注入仓储
    public SalaryLimitAttribute(IDepartmentRepository departmentRepo)
    {
        _departmentRepo = departmentRepo;
    }

    public IEnumerable<ValidationResult> Validate(ValidationContext validationContext)
    {
        var person = validationContext.ObjectInstance as Person;
        if (person == null)
        {
            yield return new ValidationResult("验证对象类型错误");
            yield break;
        }

        var department = _departmentRepo.GetById(person.DepartmentId);
        if (department == null)
        {
            yield return new ValidationResult("指定的部门不存在");
            yield break;
        }

        if (person.Salary > department.MaxAllowedSalary)
        {
            yield return new ValidationResult($"该部门最高薪资上限为{department.MaxAllowedSalary}，当前薪资超出限制");
        }
    }
}

在ASP.NET Core中，需要把这个验证属性注册为服务：

// Program.cs/Startup.cs
services.AddScoped<SalaryLimitAttribute>();

3. 使用FluentValidation实现（更灵活的验证逻辑） #

如果你的项目已经在用FluentValidation库，这种跨模型验证会更简洁易维护：

public class PersonValidator : AbstractValidator<Person>
{
    private readonly IDepartmentRepository _departmentRepo;

    public PersonValidator(IDepartmentRepository departmentRepo)
    {
        _departmentRepo = departmentRepo;

        // 针对Salary的验证规则
        RuleFor(p => p.Salary)
            .MustAsync(async (person, salary, cancellation) =>
            {
                var department = await _departmentRepo.GetByIdAsync(person.DepartmentId, cancellation);
                return department != null && salary <= department.MaxAllowedSalary;
            })
            .WithMessage((person, salary) => 
                $"该部门最高薪资上限为{_departmentRepo.GetById(person.DepartmentId)?.MaxAllowedSalary ?? 0}，当前薪资超出限制")
            .WithMessage("指定的部门不存在");
    }
}

别忘了注册验证器：

services.AddScoped<IValidator<Person>, PersonValidator>();

注意事项 #

• 确保Department类中的目标属性是public修饰的，能被验证器访问
• 涉及数据库查询时优先用异步方法，避免阻塞主线程
• 必须处理Department不存在的情况，防止空引用异常

内容的提问来源于stack exchange，提问作者Vaibhav