Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modifying conditional breakpoints while debugging does not work due to VSCode change #2428

Closed
WardenGnaw opened this issue Jul 20, 2018 · 2 comments

Comments

@WardenGnaw
Copy link
Contributor

Environment data

dotnet --info output:
.NET Core SDK (reflecting any global.json):
Version: 2.1.400-preview-009088
Commit: 0ef0b3296b

Runtime Environment:
OS Name: Windows
OS Version: 10.0.16299
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\2.1.400-preview-009088\

VS Code version: 1.25.1

C# Extension version: v1.15.2

Steps to reproduce

Create C# project and create a conditional breakpoint that will be true. Start debugging. Once you hit the breakpoint, change it to a false statement. F5.

Expected behavior

Once it becomes a false statement, it should not hit the breakpoint.

Actual behavior

It will always hit the breakpoint due to the original condition

Issue reason:

VSCode changed how they updated breakpoints. Instead of removing then adding a new breakpoint, they use the same breakpoint id.

See: microsoft/vscode#42200

@oishiimendesu
Copy link

why closed this issue?
The conditional breakpoints doesn't work yet with c#.

@gregg-miskelly
Copy link
Contributor

@menorless If you are seeing issues with conditional breakpoints, please open a new issue with details. The problem that this issue tracked was fixed in 1.16.

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

No branches or pull requests

3 participants