dotnet-nlog-logging

Standardize NLog logging in .NET by injecting NLog.ILogger as the first constructor parameter, resolving it via DI, and applying deferred formatting. This enforces consistent logger usage and configuration across backend services and libraries.

Configure NLog with Autofac by registering NLog.ILogger through the dependency injection container and setting up the NLog.config file. This ensures the logger is properly resolved and applied uniformly across the .NET project.

Use NLog.ILogger instead of Microsoft.Extensions.Logging.ILogger to avoid interface mismatches. Enforcing the native NLog interface ensures consistent structured logging practices and direct framework integration across all project components.

Best practices for NLog logging calls include using deferred formatting to prevent unnecessary string allocations and applying appropriate log levels. Injecting the logger as the first constructor parameter guarantees consistent DI-resolved usage.

Yes, these NLog logging conventions apply to typical .NET libraries and services that rely on dependency injection. The guidelines ensure the logger is resolved via DI and standardized across all dependent components.

The logger should be the first constructor parameter to enforce a consistent dependency injection pattern across .NET projects. This convention reduces runtime errors by clearly separating logging infrastructure from business dependencies.