microsoft / microsoft/vscode-dotnettools
Unable to hit breakpoints when debugging .NET iOS project in VS Code
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 321
- Forks
- 54
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 2
Description
Describe the Issue
Breakpoints are working in the main project (.csproj) but not in referenced/sub-projects.
Even though .dll and .pdb files are generated, breakpoints in those projects are ignored.
The application runs, and Console.WriteLine logs from the sub-projects appear in the debug console, confirming the code is executed.
Tried adjusting both launch.json and project (.csproj) debug settings, but no change.
Steps To Reproduce
- Open the .NET iOS project in VS Code.
- Set a breakpoint in .cs.
- Run the project in debug mode (F5).
- Observe that Console.WriteLine outputs are visible, but breakpoints are never hit.
Expected Behavior
Breakpoints should be hit when execution reaches the specified line.
Environment Information
- OS: (macOS 15.6.1)
- VS Code version: (1.103.2)
- .NET SDK version: (8.0.300)
- iOS SDK / Xcode version: (Xcode 16.4, iOS 18.5 SDK)
- Debugger / Extension used: (.NET MAUI, C#, C# Dev Kit and .NET Install Tool)
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.
Research direction
Reproduce the issue in VS Code with the .NET iOS project described, then inspect launch.json and the referenced project’s .csproj settings. Verify that code from the referenced project executes and that a breakpoint in .cs is ignored; the issue is done when those breakpoints are hit during F5 debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, ios, vscode
- Domain
- devtools, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100