Troubleshooting application crash issues with Application Verifier Tool

Application crash issues can be somewhat tricky to resolve – especially if we’re dealing with a third party application. This post look at the Application Verifier tool and how it can be leveraged to troubleshoot application issues, or for testing application compatibility beyond most normal use-case scenarios. At this point, it’s probably a good idea to […]

Application crash issues can be somewhat tricky to resolve – especially if we’re dealing with a third party application. This post look at the Application Verifier tool and how it can be leveraged to troubleshoot application issues, or for testing application compatibility beyond most normal use-case scenarios. At this point, it’s probably a good idea to differentiate managed and unmanaged code.  Unmanaged code is essentially an executable that loads into memory – like NOTEPAD.EXE.  Managed code on the other hand, is code that has its execution managed by the .NET Framework Common Language Runtime.  A quick word on the difference in support for the two - if you are working on an issue with managed code, App Verifier would not be the right tool, and you should engage our Developer Support group for assistance.

More infoDownload | MSDN: Using Application Verifier within your Software Development Life Cycle | Full Article