IoCTools.FluentValidation 1.5.1

IoCTools

A Roslyn source generator that lets each service declare its own lifetime, dependencies, and registration intent with small attributes. IoCTools emits constructors, service registrations, and analyzers at build time—no reflection, no runtime scanning.

Highlights

• Self-describing services – [Scoped], [DependsOn<T>], [RegisterAs<…>], and [ConditionalService] live on the class, so intent never leaves the type
• Dependency sets – Implement IDependencySet to reuse dependency bundles across services
• Inheritance-aware – Derived services inherit base class lifetime; diagnostics validate across the full chain
• 100+ diagnostics – Build-time validation catches missing lifetimes, circular dependencies, lifetime mismatches, open-generic edge cases, and FluentValidation anti-patterns
• Zero reflection – Everything happens at compile time; generated code is plain C# you can inspect

Authoring Posture

• Never use [Inject] in new code.
• Never use InjectConfiguration in new code.
• Use [DependsOn<T>] for service dependencies.
• Use [DependsOnConfiguration<T>] or [DependsOnOptions<T>] for configuration dependencies.
• [Inject] and InjectConfiguration remain supported in 1.5.1 for compatibility-only migration scenarios.

Installation

dotnet add package IoCTools.Abstractions
dotnet add package IoCTools.Generator

Or directly in your project file:

<ItemGroup>
  <PackageReference Include="IoCTools.Abstractions" Version="*" />
  <PackageReference Include="IoCTools.Generator" Version="*" PrivateAssets="all" />
</ItemGroup>

What's New in v1.5.1

• First real public 1.5.x release across IoCTools.Abstractions, IoCTools.Generator, IoCTools.Tools.Cli, IoCTools.Testing, and IoCTools.FluentValidation
• Evidence-first CLI — evidence, stable artifact fingerprints/deltas, stronger validator-graph --json, structured suppress --json, and better review packets
• Open-generic support — the common typeof(IFoo<>), typeof(Foo<>) path is now a supported attribute story
• Improved diagnostics — IOC093 surfaces generator analysis failures instead of degrading silently, and IOC095 explains open-generic shared-instance fallback
• Authoring guidance — [DependsOn] / [DependsOnConfiguration] are the normal path; [Inject] / InjectConfiguration are compatibility-only
• Test fixture generation and FluentValidation support ship on the same public 1.5.1 line

Getting Started in Three Steps

1. Annotate a partial service

   [DependsOn<ILogger<EmailService>>]
   public partial class EmailService : IEmailService
   {
       public Task SendAsync(string to, string subject, string body) => Task.CompletedTask;
   }
   

   Tip: [Scoped] is implied for partial classes implementing interfaces. Add [Singleton]/[Transient] only when you want to change that default.

   Full getting started guide

2. Build – IoCTools emits Add<YourAssembly>RegisteredServices() into <AssemblyName>.Extensions.Generated.

3. Call the extension during startup

   using YourAssembly.Extensions.Generated;
   
   var builder = WebApplication.CreateBuilder(args);
   builder.Services.AddYourAssemblyRegisteredServices(builder.Configuration);
   

Common Open-Generic Pattern

[Scoped]
[RegisterAsAll]
public partial class Repository<T> : IRepository<T> where T : class
{
}

That common open-generic path is supported in 1.5.1. If you ask for InstanceSharing.Shared across open-generic interface aliases, IoCTools warns with IOC095 and falls back to valid direct registrations because Microsoft.Extensions.DependencyInjection does not support open-generic factory aliases.

Platform Support

IoCTools works with .NET Framework 4.6.1+, .NET Core 2.0+, and .NET 5+. The generator targets netstandard2.0 internally, but your service code can use any C# features your framework supports. See platform constraints for details.

Testing with IoCTools

The IoCTools.Testing package auto-generates test fixtures, eliminating mock declaration boilerplate.

using IoCTools.Testing.Annotations;

[Cover<UserService>]
public partial class UserServiceTests
{
    [Fact]
    public void Test() {
        var sut = CreateSut(); // Auto-generated
    }
}

Full testing guide

IoCTools CLI

IoCTools.Tools.Cli ships as a dotnet global/local tool (dotnet ioc-tools …). It interrogates your project with the real IoCTools generator.

Installation

dotnet pack IoCTools.Tools.Cli/IoCTools.Tools.Cli.csproj -c Release -o ./artifacts
dotnet tool install --global --add-source ./artifacts IoCTools.Tools.Cli

Commands

Full CLI reference

Before & After: Replacing DI Smells

Legacy (manual, brittle)

public class LegacyBillingService : IBillingService
{
    private readonly ILogger<LegacyBillingService> _logger;
    private readonly IHttpClientFactory _httpClients;
    private readonly BillingOptions _options;
    private readonly IConfiguration _config;

    public LegacyBillingService(
        ILogger<LegacyBillingService> logger,
        IHttpClientFactory httpClients,
        IOptionsMonitor<BillingOptions> options,
        IConfiguration config)
    {
        _logger = logger;
        _httpClients = httpClients;
        _options = options.CurrentValue;
        _config = config;
    }
}

services.AddHttpClient();
services.Configure<BillingOptions>(configuration.GetSection("Billing"));
services.AddScoped<IBillingService, LegacyBillingService>();

Problems: duplicated registrations, runtime config lookups, no analyzer guardrails.

IoCTools (attributes, analyzers, generated DI)

using IoCTools.Abstractions.Annotations;

[Scoped]
[DependsOn<ILogger<BillingService>, IHttpClientFactory, IClock>]
[DependsOnConfiguration<string>("Billing:BaseUrl", Required = true)]
[DependsOnConfiguration<int>("Billing:RetryCount", DefaultValue = "3")]
public partial class BillingService : IBillingService
{
    public async Task ChargeAsync(BillingRequest request)
    {
        using var client = _httpClientFactory.CreateClient("billing");
        // _logger, _httpClientFactory, _clock, _baseUrl, _retryCount all available
    }
}

Generated code creates the constructor, binds configuration, and registers everything via builder.Services.AddYourAssemblyRegisteredServices(configuration).

Attribute Reference

Complete attribute reference: docs/attributes.md

Key attributes: [Scoped], [Singleton], [Transient], [DependsOn<T>], [DependsOnConfiguration<T>], [DependsOnOptions<T>], [RegisterAs<T>], [ConditionalService]

Diagnostics Reference

IoCTools provides core diagnostics through IOC095, plus testing diagnostics (TDIAG-01 through TDIAG-05) and FluentValidation diagnostics (IOC100 through IOC102). See complete reference.

Error-Severity Diagnostics

View all diagnostics including warnings and info

Configuration

IoCTools reads configuration from MSBuild properties/.editorconfig. Common knobs:

See configuration reference

Samples & License

• IoCTools.Sample demonstrates every attribute, diagnostic, and configuration scenario
• Licensed under MIT. See LICENSE