dotnet --info output:
VS Code version:
C# Extension version:
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
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.
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.
@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.
Most helpful comment
Is it already available, because as of now, April 2017. conditional breakpoints are not working with Unity.