Fix Blazor WASM compatibility by replacing FrameworkReference with PackageReferences

[Copilot]

Problem

Version 2.0.3+ of Serilog.Enrichers.ClientInfo causes build failures in Blazor WebAssembly applications with the error:

error NETSDK1082: There was no runtime pack for Microsoft.AspNetCore.App available for the specified RuntimeIdentifier 'browser-wasm'.

This occurs because Blazor WASM apps run in the browser and cannot reference the full Microsoft.AspNetCore.App framework that was added unconditionally in commit e0fa4cb.

Root Cause

The library includes:

<FrameworkReference Include="Microsoft.AspNetCore.App" />

This framework reference is incompatible with the browser-wasm runtime identifier used by Blazor WebAssembly applications, but the library only actually needs specific HTTP abstractions, not the entire ASP.NET Core framework.

Solution

Replaced the problematic FrameworkReference with specific PackageReference entries:

<ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.Http" Version="2.2.2" />
    <PackageReference Include="Microsoft.AspNetCore.Http.Abstractions" Version="2.2.0" />
</ItemGroup>

This provides exactly what the enrichers need:

• IHttpContextAccessor interface from Microsoft.AspNetCore.Http.Abstractions
• HttpContextAccessor implementation from Microsoft.AspNetCore.Http

Testing

• ✅ All existing tests pass (19/19)
• ✅ Sample web app works correctly
• ✅ Blazor WASM test project builds successfully with enrichers configured
• ✅ No breaking changes to existing functionality

The fix is minimal and surgical, maintaining full backward compatibility while resolving the browser-wasm compatibility issue.

Fixes #33.

---

💡 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.