Replace LibLog with Microsoft.Extensions.Logging

[craigsmitham]

Summary

LibLog v5.0.8 is no longer maintained. Replace it with Microsoft.Extensions.Logging abstractions (ILogger<T>), which are already available via ASP.NET Core dependencies.

Motivation

• LibLog is unmaintained and predates modern .NET logging patterns
• Microsoft.Extensions.Logging is the standard logging abstraction in .NET
• We already depend on Microsoft.Extensions.DependencyInjection.Abstractions and ASP.NET Core, so ILogger<T> is readily available
• Removes a dead dependency

Tasks

• Identify all usages of LibLog in the codebase
• Replace with ILogger<T> via dependency injection
• Remove LibLog package from Directory.Packages.props
• Verify logging still works in ASP.NET Core integration and tests

[craigsmitham]

Migration Plan

Research confirms this is absolutely the right move — Microsoft.Extensions.Logging.Abstractions is the official Microsoft recommendation for library authors, and LibLog has been archived since Dec 2019.

Scope

Only 3 files use LibLog directly, with 12 total log call sites (9 debug, 2 error, 1 debug in TypeSystem):

• src/GraphZen.TypeSystem/GraphQLContext.cs
• src/GraphZen.AspNetCore.Server/GraphZenServiceCollectionExtensions.cs
• src/GraphZen.AspNetCore.Server/GraphZenApplicationBuilderExtensions.cs

Steps

1. Add Microsoft.Extensions.Logging.Abstractions dependency — add to Directory.Packages.props and reference from GraphZen.TypeSystem and GraphZen.AspNetCore.Server csproj files

2. Migrate GraphQLContext.cs — replace LogProvider.For<GraphQLContext>() with ILogger<GraphQLContext> (injected or defaulting to NullLogger<GraphQLContext>.Instance); replace Logger.Debug(...) → _logger.LogDebug(...)

3. Migrate GraphZenServiceCollectionExtensions.cs — replace LogProvider.GetCurrentClassLogger() with ILogger resolved from ILoggerFactory; replace Logger.Debug(...) → logger.LogDebug(...)

4. Migrate GraphZenApplicationBuilderExtensions.cs — replace LogProvider.GetCurrentClassLogger() with ILogger resolved from IApplicationBuilder.ApplicationServices; replace Logger.Error(exception, message) → logger.LogError(exception, message)

5. Fix string interpolation in log calls — replace $"Adding GraphQL context {contextType}" with message templates: "Adding GraphQL context {ContextType}", contextType

6. Remove LibLog — remove from Directory.Packages.props, remove reference and LIBLOG_EXCLUDE_CODE_COVERAGE from GraphZen.Infrastructure.csproj, remove using GraphZen.Logging; imports, clean generated files from obj/

7. Verify example app — SimpleBlog uses Serilog via UseSerilog() which integrates natively with Microsoft.Extensions.Logging, so it should work without changes

8. Build & test — dotnet build + dotnet test

Design Decisions

Decision	Choice
Package dependency	Microsoft.Extensions.Logging.Abstractions only (lightweight interfaces)
ILogger<T> vs ILoggerFactory	ILoggerFactory for public APIs (future-proof); ILogger<T> for DI-constructed classes
No-op default	NullLoggerFactory.Instance / NullLogger<T>.Instance when no logger provided
Source-generated logging	Optional follow-up — current call sites are simple enough