In this episode of Defrag Tools, Andrew Richards and Chad Beeder walk you through a common issues in Windows Store applications that use Interop. We use a Windows Store 8.1 app sample to show how missing code affects the stability of the process.
[00:34] - Commonly missed CLR Exceptions
[06:50] - What's an Interop application?
[09:10] - What's an HRESULT? (Microsoft; Wikipedia)
[13:23] - Samples - XAML SurfaceImageSource DirectX interop example
[18:15] - Remove the removed/reset handler to cause an HRESULT based exception
[20:21] - Add an exception handler with associated XAML TextBlock
[23:16] - Sometimes you get System.Exception, instead of the exact exception type
[25:10] - Dump of the unhandled exception... No CLR Exception (!pe)
[28:21] - Email us your issues at firstname.lastname@example.org
[29:34] - DirectX apps on old DirectX hardware
If you have a crash you don't understand, email the CAB file to email@example.com and we'll help you.
Available formats for this video:
Actual format may change based on video formats available and browser capability.
Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you can Contact Us.