Why don't I see a Xaml Binding Failure or exception logged for an invalidate StaticResource reference. #19724
Unanswered
DanTravison
asked this question in
Q&A
Replies: 1 comment
-
Some additional details: I'm creating the page from code using Activator.CreateInstance. Is this defeating some Maui or Xaml exception handling?
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I made a change to my app.xaml and inadvertently removed one of my declarations:
<x:Double x:Key="OptionFontSize">25</x:Double>
I reference it in my mainpage.xmal on a Button declaration:
FontSize="{StaticResource OptionFontSize}"
I'm usually consistent about reviewing debug output and XAML binding failures when I make changes, but I didn't recall seeing anything.
In fact, running the app in the debugger didn't report anything in either of the expected locations.
So, why isn't this reported and why don't I see an exception for it when run in the debugger?
This is more than just a curiosity; JIT debugging doesn't seem to work on my latest VS build, so I had to spend the morning researching global exception handlers for Maui and custom logging to get to the actual root cause.
I'm currently using VS Version 17.9.0 Preview 2.1 and Maui 8.0.3.
Beta Was this translation helpful? Give feedback.
All reactions