Skip to content

Conversation

@LoopedBard3
Copy link
Member

Update BlazorLocalized.csproj to allow references to prerelease net10.0 Microsoft.Extensions packages while we wait for stable packages.

This should fix the BlazorLocalized performance-ci errors we are seeing. Tested successfully locally.

@LoopedBard3 LoopedBard3 self-assigned this Oct 30, 2025
@LoopedBard3 LoopedBard3 added the bug Something isn't working label Oct 30, 2025
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds a workaround for resolving pre-release Microsoft.Extensions package dependencies when targeting .NET 10.0 in a Blazor WebAssembly project. The WebAssembly SDK requires Microsoft.Extensions packages version 10.0.0 or higher, but only pre-release versions are currently available in internal feeds, causing transitive dependency resolution failures.

  • Introduces conditional package references for Microsoft.Extensions packages using floating pre-release version syntax (10.0.0-*)
  • Applies the workaround only when targeting net10.0 framework
  • Explicitly references nine Microsoft.Extensions packages to override transitive resolution

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@LoopedBard3 LoopedBard3 enabled auto-merge (squash) October 30, 2025 21:34
@LoopedBard3
Copy link
Member Author

Just rebased to get the fix for the URI SafeDnsHost test.

@LoopedBard3 LoopedBard3 merged commit 3eae112 into dotnet:main Oct 30, 2025
79 of 80 checks passed
@LoopedBard3 LoopedBard3 deleted the FixBlazorTests branch October 30, 2025 22:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants