Eigenverft.NetLib.Logging.Bootstrap 1.0.0.5-gdfdd996480

Eigenverft.NetLib.Logging.Bootstrap

Log startup diagnostics before the host is built, using an initialized Serilog logger when available and otherwise a Microsoft logging fallback.

✨ At a glance

📦 Installation

dotnet add package Eigenverft.NetLib.Logging.Bootstrap

🚀 Quick start

Create the bootstrap logger after configuring the builder but before building the host:

using Eigenverft.NetLib.Logging.Bootstrap;
using Microsoft.Extensions.Hosting;
using Microsoft.Extensions.Logging;

var builder = Host.CreateApplicationBuilder(args);
ILogger startupLogger = BootstrapLogger.CreateLogger("Startup", builder.Configuration);
startupLogger.LogInformation(
    "Starting in {Environment}",
    builder.Environment.EnvironmentName);

using IHost host = builder.Build();
await host.RunAsync();

The first successful factory creation is cached for the process. Later configuration arguments or application logging reconfiguration do not replace the bootstrap channel. The returned factory is process-owned; callers must not dispose it.

🪵 Backend behavior

The automatic API captures the current global Serilog logger when Serilog and its Microsoft logging bridge are available and that logger is not Serilog's built-in silent default. Otherwise it uses Microsoft logging, applying the Logging section and adding Console support when the corresponding extension assemblies are available. The package has no compile-time Serilog dependency; the consuming application supplies Serilog and its bridge if it wants the automatic Serilog path.

For an explicitly required, isolated Serilog setup, the default file is AppSettings/BootstrapLoggerSettings.json beneath AppContext.BaseDirectory:

ILogger<Program> startupLogger =
    BootstrapLogger<Program>.CreateRequiredSerilogLogger();

This strict method does not fall back to Microsoft logging. The consuming application must provide Serilog core, Serilog.Settings.Configuration, Serilog.Extensions.Logging, and every sink or enricher named in the file. It reads only that JSON file and section; it does not load the host's other configuration sources. This method should be the first bootstrap-logger initialization in the process. Optional reloadOnChange updates Serilog levels and switches, but does not rebuild its sink pipeline.

LogConfigurationResolution(...) belongs to Eigenverft.NetLib.Configuration.Diagnostics. The early environment helper is in Eigenverft.NetLib.Hosting.DirectoryLayout.

To diagnose provider precedence before host construction, install Eigenverft.NetLib.Configuration.Diagnostics, then call the extension after registering configuration sources and pass the bootstrap logger:

using Eigenverft.NetLib.Configuration.Diagnostics;
using Eigenverft.NetLib.Logging.Bootstrap;
using Microsoft.Extensions.Hosting;
using Microsoft.Extensions.Logging;

var builder = Host.CreateApplicationBuilder(args);
ILogger startupLogger = BootstrapLogger.CreateLogger("Startup", builder.Configuration);
builder.LogConfigurationResolution(startupLogger);

using IHost host = builder.Build();
await host.RunAsync();

This is an optional package pairing, not a dependency; the diagnostics report provider origins and key-shadow chains, never configuration values.

🎯 Target frameworks

• net8.0
• net10.0

A .NET 9 consumer can use the compatible net8.0 asset.

🔗 Project links

• Source project
• Solution documentation
• Repository

📄 License

MIT