Introduction

Yes, log4net can be configured programmatically without an external XML config file. This is useful in dynamic environments, multi-tenant apps, tests, and applications that generate logging targets at runtime. Code-based configuration gives more control, but it also increases responsibility: you must set appenders, layouts, levels, and repository initialization explicitly. If done carefully, this approach is predictable and versionable within code review workflows.

Core Sections

Minimal code-based setup

You can build appenders and attach them to the root logger in startup code.

1using log4net;
2using log4net.Appender;
3using log4net.Layout;
4using log4net.Repository.Hierarchy;
5
6var hierarchy = (Hierarchy)LogManager.GetRepository();
7var patternLayout = new PatternLayout("%date %-5level %logger - %message%newline");
8patternLayout.ActivateOptions();
9
10var consoleAppender = new ConsoleAppender
11{
12    Layout = patternLayout
13};
14consoleAppender.ActivateOptions();
15
16hierarchy.Root.AddAppender(consoleAppender);
17hierarchy.Root.Level = log4net.Core.Level.Info;
18hierarchy.Configured = true;
19
20ILog log = LogManager.GetLogger(typeof(Program));
21log.Info("log4net configured from code");

This avoids XML and keeps configuration in your bootstrapping path.

Add file appender programmatically

1var fileAppender = new RollingFileAppender
2{
3    File = "logs/app.log",
4    AppendToFile = true,
5    RollingStyle = RollingFileAppender.RollingMode.Size,
6    MaxSizeRollBackups = 5,
7    MaximumFileSize = "10MB",
8    StaticLogFileName = true,
9    Layout = patternLayout
10};
11fileAppender.ActivateOptions();
12hierarchy.Root.AddAppender(fileAppender);

Ensure filesystem permissions are valid before logging begins.

Environment-specific configuration

You can branch by environment to set different log levels.

bool isProd = Environment.GetEnvironmentVariable("ASPNETCORE_ENVIRONMENT") == "Production";
hierarchy.Root.Level = isProd ? log4net.Core.Level.Warn : log4net.Core.Level.Debug;

This is useful for reducing noise in production while keeping rich dev logs.

Testing benefits

Code-based setup is easy to initialize in integration tests with temporary appenders and deterministic output paths.

When XML is still useful

External config files can be changed without recompilation and are familiar for operations teams. Choose based on deployment model and ownership.

Common Pitfalls

• Forgetting ActivateOptions() on layout/appenders and getting missing or malformed logs.
• Not setting hierarchy.Configured = true, resulting in silent fallback behavior.
• Initializing log4net too late in app startup and missing early errors.
• Hardcoding file paths that fail in container or restricted environments.
• Mixing XML and code configuration unintentionally and causing duplicate appenders.

Verification Workflow

After switching to code-based configuration, validate startup logs, rotation behavior, and level filtering in each environment profile. Add one integration test that asserts log output format and one smoke check that confirms writable log target paths. Monitor for duplicate log lines after deployment.

11. Start app and verify first log entries
22. Check level filtering by environment
33. Trigger rollover and validate file policy
44. Confirm no duplicate appenders
55. Add automated logging smoke tests

Production Readiness Checklist

Before considering the implementation complete, run a repeatable readiness pass that validates correctness, failure handling, and operational behavior in the same environment class where this solution will run. Start with a deterministic happy-path example and then exercise one malformed input and one resource-constrained scenario. Capture structured output such as status codes, key counters, and timing metrics so regressions are visible across revisions.

Document expected behavior boundaries in plain language so future maintainers can quickly understand what is guaranteed and what is best-effort. If configuration affects behavior, include the exact setting names and safe defaults in your runbook. For team workflows, add one lightweight automated check in CI to enforce these expectations on every change and keep debugging effort low when dependencies or runtime versions change.

11. Validate normal input path
22. Validate malformed or missing input path
33. Validate constrained-resource behavior
44. Record timing and error metrics
55. Confirm rollback or fallback behavior
66. Add CI smoke check for regression detection

Summary

log4net can be fully configured in code and works well when dynamic or environment-driven behavior is required. The setup is explicit and testable, but requires careful initialization and validation. If you manage appenders and levels intentionally, code-based configuration is a practical alternative to XML.