Conditional Breakpoints #8984
Unanswered
garrettpauls
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This may be more accurate to target at Visual Studio, but it's a pain point I've run into as I get deeper into WinUI development so I'm going to ask here to start.
Currently trying to set a conditional breakpoint on almost any property on any built in WinUI control fails an error similar to "Evaluation of method Microsoft.UI.Xaml.FrameworkElement.get_Name() calls into native code. Evaluation of native methods in this context is not supported."
I understand why this happens (I appreciate the descriptive error message), but it does hamper the debugging workflow when coming from WPF where I could set a conditional breakpoint on almost anything.
My question is: are there any plans to allow conditional breakpoints on WinUI control properties in Visual Studio? Or is that off the table since WinUI is mostly calls into unmanaged code?
As a follow up: are there any good workarounds to this? Currently when I know I need to do a conditional breakpoint I'll store the value off into a temporary variable and break on that, but it's inconvenient when you realize you need this on the fly and haven't written code accordingly.
Beta Was this translation helpful? Give feedback.
All reactions