Skip to content

Conversation

@ilonatommy
Copy link
Member

Similar to #52517 but fixes dotnet/aspnetcore#65261.

Testing:

  • build sdk
  • run dotnet pack ".\src\BuiltInTools\HotReloadAgent.WebAssembly.Browser\Microsoft.DotNet.HotReload.WebAssembly.Browser.csproj" -c Debug -o ".\artifacts\packages\Debug\Shipping" /p:Version=11.0.100-preview.1.26078.107 to create the missing net11 package
  • take it and copy it to local net11 nuget cache Expand-Archive -Path $nupkg -DestinationPath "C:\Nuget\microsoft.dotnet.hotreload.webassembly.browser\11.0.100-preview.1.26078.107" -Force
  • Rerun the steps from the issue and see the problem is gone

@ilonatommy ilonatommy requested review from Copilot and tmat January 29, 2026 13:01
@ilonatommy ilonatommy added the Area-AspNetCore RazorSDK, BlazorWebAssemblySDK, StaticWebAssetsSDK label Jan 29, 2026
@dotnet-policy-service
Copy link
Contributor

Thanks for your PR, @@ilonatommy.
To learn about the PR process and branching schedule of this repo, please take a look at the SDK PR Guide.

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 .NET 11.0 target framework support for the HotReload WebAssembly Browser package to fix a missing package version issue when building .NET 11 WebAssembly applications.

Changes:

  • Added AgentTargetFrameworkV11 property for .NET 11.0 assemblies injected into apps
  • Updated WebAssembly.Browser project to multi-target both net10.0 and net11.0
  • Clarified that AgentTargetFrameworkV10 is specifically for .NET 10.0 (not 10.0+)

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
src/BuiltInTools/Watch/TargetFrameworks.props Adds AgentTargetFrameworkV11 property and updates V10 comment to be more precise
src/BuiltInTools/HotReloadAgent.WebAssembly.Browser/Microsoft.DotNet.HotReload.WebAssembly.Browser.csproj Imports TargetFrameworks.props and multi-targets net10.0 and net11.0 to ensure compatibility with both runtime versions

Copy link
Member

@tmat tmat left a comment

Choose a reason for hiding this comment

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

Do we actually need to target .NET 11? Wouldn't pinning to net10 work?

@tmat
Copy link
Member

tmat commented Jan 29, 2026

Let's remove the package instead: @maraf is working on it here: #52710

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-AspNetCore RazorSDK, BlazorWebAssemblySDK, StaticWebAssetsSDK

Projects

None yet

Development

Successfully merging this pull request may close these issues.

After installing .NET 11.0 SDK, Running the 10.0 Blazor WebAssembly - memory access out of bounds

2 participants