Description
Suggested new feature or improvement
Set the FailFastOnErrors property so that XAML errors will result in immediate crashes (thereby enabling easier diagnosis).
Scenario
This is feedback from the WinAppSDK folks who helped investigate some recent bugs, so filing this issue to help track it. The idea is to use the property documented below in Dev Home so that it is easier to find errors earlier and with more context, which is especially useful in cases where those errors might otherwise be ignored.
Additional details
The documentation indicates that this can be set for apps in the Store as well. So we would likely want to do this in a progressive fashion (e.g., set this property, run through our test scenarios and see what crashes get surfaced, fix those, test again, etc.). Once we have a good baseline, we could consider enabling this globally in published versions of the application.