microsoft / microsoft/vscode-dotnettools
When debugging the Blazor WebAssembly project in .NET11 RC2, the breakpoint in Counter.razor file can't be hit
Open
@LittleLittleCloud is already working on this.
Since Sep 16, 2026.
- Dominant language
- No language data
- Stars
- 321
- Forks
- 54
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 2
Description
Regression info:
- Works well with .NET11 Preview 5
- Reproduced with CDK v3 prerelease version 3.33.194 with C# 2.151.28
- Reproduced with CDK v11 (main) version 11.0.26-g390db5 with C# (main) 2.152.19
Install Steps
- OS: windows x64
- Install VS Code Stable 1.137.0
- Install C# Dev Kit V3 Sept release 3.40.202, and C# 2.151.28
- Install .Net 11.0 RC2
- Add feed
Repro Steps
- Open a normal Command Prompt (do not run as administrator).
- Create a Blazor Web App - WebAssembly project and open it with vs code
dotnet new blazor -int WebAssembly -o BlazorWASM cd BlazorWASM code . - Open the
BlazorWASM.Client/Pages/Counter.razorfile, place a breakpoint at method currentCount++; (line 16) - Navigate to the explorer, right click the *.csproj file > debug > Start New Instance
- After the project opens in the browser, click the "Click me" button in Counter page.
Note:
- This does not repro with Blazor Web App - Server/Auto project and Blazor WebAssembly Standalone project
- This does not repro on .NET 10/9 projects
Actual:
Expected:
Breakpoint will be hit
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.