Sample App Better Exception Handling

[michael-hawker]

Describe the problem this feature would solve

If a developer types something unexpected in the XAML live editor this can crash the sample app. This can be directly from an issue with the XAML Parsing from XamlReader OR it can be an issue when something invalid was parsed but then added to the Visual Tree. In either case, it'd be nice to not take down the whole sample app when that occurs.

Describe the solution

When we start a render pass, we should mark a flag. Then if we hit an unhandled exception within a few seconds of an edit, we should check for that flag and handle the exception at the app level.

This would help us with scenarios where the developer's XAML performs something unexpected and normally would crash the app.

We could add better logging here as well to try and understand more of what issues are coming up. I'm not sure if there's an MVP we can do for 7.0 to just help with minimizing crashes vs. actually providing visual feedback.

This is something I should do and been thinking about for XAML Studio as well, so not sure if there's overlap as we move forward with redesigning the sample app for 7.1.

[ghost]

Hello, 'michael-hawker! Thanks for submitting a new feature request. I've automatically added a vote 👍 reaction to help get things started. Other community members can vote to help us prioritize this feature in the future!