dotnet-extensions-logging

Enforce ILogger<T> logging conventions by standardizing constructor parameter ordering, applying null-checks, and validating structured logging patterns across all injected service classes in .NET applications.

Structure constructor parameters by placing ILogger<T> as the first argument, followed by null-checks to ensure safe, structured logging and consistent dependency injection across typical application layers.

Structured logging with Microsoft.Extensions.Logging uses ILogger<T> to defer message formatting, properly log exceptions, and integrate with common DI containers, ensuring consistent and maintainable logging practices.

This convention applies to dependency-injected classes and typical application layers, ensuring safe structured logging. It prescribes constructor ordering and null-checks specifically designed for DI container integration scenarios.

The logger should be the first parameter to enforce consistent ILogger<T> usage conventions across .NET projects, reducing logging inconsistencies and improving maintainability by standardizing dependency injection patterns.

The conventions specifically target dependency-injected classes using ILogger<T>, covering error handling scenarios and common DI containers, but may not apply to static classes or non-DI architectural patterns.