Fix CA1848 documentation: Update link and add code examples

[Copilot]

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.

---

Internal previews

📄 File	🔗 Preview link
docs/fundamentals/code-analysis/quality-rules/ca1848.md	CA1848: Use the LoggerMessage delegates

[IEvangelist]

Two code formatting nits, otherwise

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 issues. Other issues are also a high priority. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.