TSLAppLogger 3.1.0

TSLAppLogger

A production-safe, non-blocking logging library for .NET Framework 4.8, designed for Windows Services, * telecom systems*, and long-running backend applications.

TSLAppLogger is built with one rule above all others:

Logging must never impact application stability.

🚀 Quick Start

Install via NuGet

Install-Package TSLAppLogger

dotnet add package TSLAppLogger

📦 Package Information

• Package Name: TSLAppLogger
• Version: 3.1
• Target Framework: .NET Framework 4.8

✨ Key Features

• Asynchronous, non-blocking logging
• Logger APIs never throw exceptions
• Safe for Windows Services and always-on systems
• File-based logging with automatic fallback
• Windows Event Log support for critical failures
• Emergency logging when file logging is unavailable
• Service lifecycle logging (start / stop / fatal)
• Minimal CPU and memory overhead

🧠 Design Philosophy

TSLAppLogger is designed for worst-case production scenarios:

• Logging failures are silently handled
• Application execution is never interrupted
• Safe to use in:
  • try / catch blocks
  • Startup code
  • Shutdown paths
  • Crash handling logic

🧩 Initialization

Initialize the logger once during application or service startup.

TSLAppLogger.Initialize();

Notes

• Safe to call multiple times
• Does not block
• Does not throw exceptions

📝 Writing Logs

TSLAppLogger.Debug("Debug message");
TSLAppLogger.Info("Application started");
TSLAppLogger.Warn("Configuration file missing, using defaults");
TSLAppLogger.Error("Operation failed");
TSLAppLogger.Fatal("Critical failure");

All logging calls:

• Are asynchronous
• Never throw
• Never block the calling thread

🧯 Logging Exceptions

Logging exceptions is safe and recommended.

try
{
    ProcessRequest();
}
catch (Exception ex)
{
    TSLAppLogger.Error("Unhandled exception occurred", ex);
}

• Full exception details are logged
• Application flow is never affected

🪟 Windows Service Usage

TSLAppLogger is optimized for Windows Services.

Service Start

protected override void OnStart(string[] args)
{
    TSLAppLogger.Initialize();
    TSLAppLogger.Info("Service started");
}

Service Stop

protected override void OnStop()
{
    TSLAppLogger.Info("Service stopped");
}

Fatal Service Error

catch (Exception ex)
{
    TSLAppLogger.Fatal("Service crashed", ex);
}

🪵 Log Output

Default Locations

• Application Logs

  • Standard operational logs

• ServiceEventLogs

  • Service lifecycle events
  • Emergency and fallback logs
  • Fatal failures

Each entry includes:

• Timestamp
• Machine name
• Process ID

Directories are created automatically if missing.

🪟 Windows Event Log

For critical scenarios, logs may also be written to the Windows Event Log:

• Service startup failures
• Fatal runtime errors
• Emergency fallback conditions

Event log writes are safe and non-blocking.

🛡️ Reliability Guarantees

• Logger never throws exceptions
• Logging failures never stop the application
• Automatic fallback when file logging fails
• Safe during startup, runtime, and shutdown

Logging will never be the reason your application fails.

⚙️ Performance

• Fully asynchronous
• Minimal locking
• Low memory allocation
• Safe for high-throughput, multi-threaded systems

🎯 Recommended Use Cases

• Windows Services
• Telecom and network systems
• Background workers
• Long-running backend processes
• Mission-critical production applications

🧾 Summary

TSLAppLogger is a production-first logging library focused on:

• Stability
• Predictability
• Safety

If your system must stay online no matter what, TSLAppLogger is built for that.