You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the MahApps ColorCanvas results in 14 binding expressions errors when the control is displayed. VS2019 shows them in the new XAML Binding Failures tool (Debug > Windows > XAML Binding Failures). Alternatively, you add a TraceListener via PresentationTraceSources.DataBindingSource (this is what we use during development to avoid binding errors).
Steps to reproduce
Create a new WPF application (I used framework, but probably doesn't matter) and use a ColorCanvas, e.g. using the sample code from the MahApps ColorPicker Documentation.
14 binding expressions errors show up (see screenshot below). Using a TraceListener in combination with Debugger.Break(); calls completely kills the development experience.
Describe the bug
Using the MahApps
ColorCanvas
results in 14 binding expressions errors when the control is displayed. VS2019 shows them in the new XAML Binding Failures tool (Debug > Windows > XAML Binding Failures). Alternatively, you add aTraceListener
viaPresentationTraceSources.DataBindingSource
(this is what we use during development to avoid binding errors).Steps to reproduce
Create a new WPF application (I used framework, but probably doesn't matter) and use a
ColorCanvas
, e.g. using the sample code from the MahApps ColorPicker Documentation.Expected behavior
No binding expression errors occur.
Actual behavior
14 binding expressions errors show up (see screenshot below). Using a
TraceListener
in combination withDebugger.Break();
calls completely kills the development experience.Environment
Screenshots
The text was updated successfully, but these errors were encountered: