CentralLogger.Client 1.0.0

CentralLogger.Client

This is the all-in-one package for adding CentralLogger to a .NET application. It includes:

• CentralLogger.Client.dll and CentralLogger.Abstractions.dll.
• The complete framework-dependent Windows x64 CentralLogger.Service payload.
• Build-transitive deployment that copies the service to service\ beside your application output.
• Durable client spooling, automatic reconnect, installed-service startup, and portable-service startup.

Requirements

• .NET 8 or later application.
• Windows x64 for the included service executable.
• UAC approval when portable service mode first starts and needs access to the machine-wide ProgramData database.

Install

dotnet add package CentralLogger.Client --version 1.0.0

For a local package feed:

dotnet add package CentralLogger.Client --version 1.0.0 --source C:\path\to\publish\nuget

Build the application once. The output will contain:

YourApplication.exe
service\
  CentralLogger.Service.exe
  CentralLogger.Service.dll
  appsettings.json
  ...runtime dependencies...

Start logging

Initialize once at application startup:

using CentralLogger;

Logger.Initialize("ATMApplication");

Create one logger for each class or component:

private static readonly Logger Log =
    new("CashDispenser", "$Workfile: CashDispenser.cs $", "$Revision: 1.0 $");

Write logs without waiting for the service or database:

Log.Debug("Starting dispense operation.");
Log.Info("Dispense completed.");
Log.Warning("Cassette level is low.");
Log.Error(exception, "Dispense failed.");
Log.Write("CashPresented", "Cash was presented to the customer.");

Applications do not call FlushAsync during normal use. Entries are queued durably and delivered in the background. A bounded automatic drain runs at process exit, and unacknowledged entries remain in the client spool for replay.

Service behavior

All applications connect to the same local named-pipe service and write to one central database. The default database is:

C:\ProgramData\Company\CentralLogger\CentralLogs.db

If the installed CompanyCentralLogger Windows service is unavailable, the client locates service\CentralLogger.Service.exe from the application output and starts it in portable mode. Multiple applications may contain the payload; a machine-wide mutex ensures only one writer service is active.

For a permanent Windows-service installation, run the included service\Install-Service.ps1 from an elevated PowerShell session. The service configuration is service\appsettings.json; database, retention, encryption, recovery, and archive settings belong to the service, not application projects.