Skip to content

Log4Net

Log4Net is supported as an alternative logging provider where legacy compatibility or existing operational tooling requires it.

Positioning

Use Log4Net when:

  • an existing deployment already standardizes on Log4Net appenders;
  • migration from older .NET services is incremental;
  • a template explicitly enables the Log4Net feature flag.

Prefer Serilog for new services that need modern structured logging, JSON container logs, and first-class enrichment.

ConnectSoft Guidance

  • Keep Log4Net optional and feature-flag controlled.
  • Do not mix provider-specific configuration with canonical logging concepts.
  • Preserve correlation and redaction expectations regardless of provider.
  • Document appender and configuration file details in implementation docs.

Template Responsibilities

BaseTemplate should document package wiring, feature flags, registration methods, and configuration files. Layer 3 templates should document only whether Log4Net is inherited, disabled, or extended.