Breakpoint is not hit when debugging a .NET 10 console project with Containers: .NET Launch
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Reproduce the issue with a .NET 10 console project, Docker support, Program.cs, and the Containers: .NET Launch configuration, then compare it with .NET Core Launch (console), where the breakpoint works. Trace the container debugging setup and verify that the breakpoint on Console.WriteLine("Hello, World!") is hit when the fix is complete.
Written by the indexing model from the issue text.
Description
OS: Win 10
Build Version: 20260924.1
Repro Steps:
- Create a .NET10 console project
- Add Docker support to the project
- Set a breakpoint on the Console.WriteLine("Hello, World!"); line in Program.cs.
- Select Containers: .NET Launch and start debugging.
- Observe whether the breakpoint is hit or not
Expect:
The breakpoint should be hit when debugging the .NET console project with Containers: .NET Launch
Actual:
The breakpoint is not hit when debugging with Containers: .NET Launch
More Info:
This issue doesn't repro when debugging with .NET Core Launch (console)
- Dominant language
- TypeScript
- Stars
- 147
- Forks
- 93
- Avg merge
- 9h 16m
- Merged PRs (30d)
- 14
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from microsoft/vscode-containers
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/vscode-containers#655 ·
Maintainers usually reply within 1 day
-
Compose Down fails for projects started with multiple --env-file argumentsPossibly taken @sylvesterkaczmarek claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/vscode-containers#653 ·
Maintainers usually reply within 1 day
-
Add localization (i18n) support, starting with Simplified Chinese (zh-cn)Possibly taken @linghengqian claimed this 3 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/vscode-containers#648 · 3 comments ·
Maintainers usually reply within 1 day
-
.NET AT-CTI blocked external
Difficulty 3/5 1-2 days Newbie friendliness 72/100
microsoft/vscode-containers#605 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
engineering
Difficulty 4/5 3-5 days Newbie friendliness 38/100
microsoft/vscode-containers#594 · 1 comment ·
Maintainers usually reply within 1 day
All issues in microsoft/vscode-containers
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
backnotprop/plannotator#2914 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dsh-tauri-desk/deepseek-harness-desktop#1477 · 1 comment ·
-
[docs] RELEASE.md: wrong branch name, no check that the prepare PR merged with the right subject, manual publish stepPossibly taken @albertteoh claimed this today. Opendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
jaegertracing/jaeger-ui#4739 ·
Maintainers usually reply within 1 day