Dev home plugins should have a way to communicate extended error messages #565
Description
Dev Home version
No response
Windows build number
No response
Other software
No response
Steps to reproduce the bug
This is related to the linked bug. But when that bug is resolved, you will still not get the experience where the exception from the plugin marshaled to Dev Home has the detailed error message that it was initially thrown with. This is because the exception is translated to an WinRT error which is an HRESULT and an error info. The latter is only used to improve diagnosability in a debugger / dump and isn't used by C# to rehydrate the exception message especially for out of proc scenarios. In addition, the error info marshaling is best effort as it is a diagnosability feature. Due to that, Dev Home shouldn't rely on the exception message in such scenarios if it needs something to show to the user.
Instead, Dev Home should have something like a Result return for such APIs and that should have some ExtendedError or similar property which plugins and Dev home can rely on to communicate known errors to display to the user.
See the following for guidance:
https://www.osgwiki.com/wiki/WinRT_API_Design_Patterns#Return_a_rich_error_object
https://www.osgwiki.com/wiki/WinRT_API_Design_Patterns#Extended_Errors
Please see other feedbacks in userfeedback Vso for feedbacks that are tracked by this work item.
Expected result
No response
Actual result
No response
Included System Information
No response
Included Extensions Information
No response