-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable FailFastOnErrors property to better improve error diagnosis #3019
Labels
Comments
Besides the errors on startup and shutdown, I'm seeing one after clicking "set up local machine" in Machine configuration, although it doesn't bring down DH. |
This was referenced Jun 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
https://learn.microsoft.com/en-us/uwp/api/windows.ui.xaml.debugsettings.failfastonerrors?view=winrt-22621
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.
Tasks
FailFastOnErrors
is true. CommunityToolkit/Windows#438The text was updated successfully, but these errors were encountered: