This PR improves the CA1848 rule documentation by updating an incorrect link and adding practical code examples to help developers understand how to fix violations.

Changes Made

Updated LoggerMessage Link

The rule description previously linked to the LoggerMessage API documentation, but now correctly points to the high-performance logging article that provides comprehensive guidance on implementing the pattern:

• Before: Links to Microsoft.Extensions.Logging.LoggerMessage API docs
• After: Links to /dotnet/core/extensions/high-performance-logging article

Added Code Examples

Added clear before/after examples in the "How to fix violations" section showing:

Code that violates CA1848:

public class SomethingDoer
{
   private readonly ILogger _logger;
   public SomethingDoer(ILogger<SomethingDoer> logger)
   {
    _logger = logger;
   }

   public void DoSomething()
   {
       _logger.LogInformation("We did something!");  //This call violates CA1848
   }
}

Corrected code using LoggerMessage pattern:

public partial class SomethingDoer
{
   private readonly ILogger _logger;
   public SomethingDoer(ILogger<SomethingDoer> logger)
   {
    _logger = logger;
   }

   public void DoSomething()
   {
       Log_DidSomething();
   }

   [LoggerMessage(Level = LogLevel.Information, Message = "We did something!")]
   private partial void Log_DidSomething();
}

These examples demonstrate the key differences:

• Using partial class declaration
• Replacing direct ILogger extension method calls with generated delegate methods
• Using the [LoggerMessage] attribute to define the log message template

The documentation now provides developers with concrete examples they can reference when fixing CA1848 violations in their code.

Fixes #46239.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.