-
Notifications
You must be signed in to change notification settings - Fork 677
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
Debugger: Conditional breakpoint not supported by this debug type #497
Comments
@GraceDong conditional breakpoints are just about to go in, but there aren't in yet. |
@chuckries do you want to resolve this once you checkin? |
@gregg-miskelly sure. |
This will be available in the next release. |
Is it already available, because as of now, April 2017. conditional breakpoints are not working with Unity. |
Going with what @xCyborg said. I'm not able to use conditional breakpoints with Unity 5.4.3f1. Is this an issue with this extension or the Debugger for Unity extension? |
For debugging, this extension only supports .NET core (and limited .NET Full Framework on Windows) development. AFAIK Unity doesn't use either of these, so you want a different debugger. |
Environment data
dotnet --info
output:VS Code version:
C# Extension version:
Steps to reproduce
1 Add a conditional breakpoint at line of " _appSettings = options.Value; " in HomeController.cs
and edit that breakpoint with condition of "1<0"
2 Press F5 to start debugging
Expected behavior
The conditional breakpoint I just added shouldn't be hit in editor window. I input a false expression, so the breakpoint would not be hit.
Actual behavior
The conditional breakpoint would be hit and error message show "Conditional breakpoints not supported by this debug type". I don't know whether the conditional breakpoint is supported on CoreCLR.
The text was updated successfully, but these errors were encountered: