Windows Mobile Application Verifier Test, the Stepping Stone to the Windows Marketplace for Mobile
Developer registration for the Windows Marketplace for Mobile kicked off in May and as of today, all you developers out there can submit your Windows Mobile application. There are two catches though. The first one, as Senior Director for Mobile Platform Services Product Management with Microsoft, Todd Brix, explained earlier this month, is that the Windows Marketplace for Mobile is on track to accept app submissions as of July 17th, but only in select countries.
These select countries, 29 in total, are: Australia, Austria, Belgium, Brazil, Canada, Denmark, Finland, France, Germany, Greece, Hong Kong SAR, India, Ireland, Italy, Japan, Luxembourg, Mexico, New Zealand, Netherlands, Norway, Poland, Portugal, Singapore, Spain, Sweden, Switzerland, Taiwan, United Kingdom, US of A.
The second catch is that your WinMo app must first pass the Windows Mobile Application Verifier test before it will be accepted to the Windows Marketplace. And to be more specific, while the Windows Mobile Application Verifier app runs, your app must be able to perform is primary and secondary functions.
Additional, technical details, are provided by Microsoft’s Eric Nelson: “AppVerifier needs to be configured to detect heap corruption and invalid locks usage, including critical section use. The specific conditions that must be met in order for the application to pass the AppVerifier test are:
- The application must not break into the debugger, crash, or fail when Application Verifier Heaps, Locks and Handles related tests are performed.
- The application must not have any invalid pointers associated with the main executable.”
The goal of the Windows Mobile Application Verifier app is to test whether your app is stable and to detect common programming mistakes. It will assess the app's stability, pinpoint memory leaks, handle leaks, and some forms of heap corruption. It will attach to the app while said app is running and attempt to identify problems and issues that the developer may have overlooked.
These select countries, 29 in total, are: Australia, Austria, Belgium, Brazil, Canada, Denmark, Finland, France, Germany, Greece, Hong Kong SAR, India, Ireland, Italy, Japan, Luxembourg, Mexico, New Zealand, Netherlands, Norway, Poland, Portugal, Singapore, Spain, Sweden, Switzerland, Taiwan, United Kingdom, US of A.
The second catch is that your WinMo app must first pass the Windows Mobile Application Verifier test before it will be accepted to the Windows Marketplace. And to be more specific, while the Windows Mobile Application Verifier app runs, your app must be able to perform is primary and secondary functions.
Additional, technical details, are provided by Microsoft’s Eric Nelson: “AppVerifier needs to be configured to detect heap corruption and invalid locks usage, including critical section use. The specific conditions that must be met in order for the application to pass the AppVerifier test are:
- The application must not break into the debugger, crash, or fail when Application Verifier Heaps, Locks and Handles related tests are performed.
- The application must not have any invalid pointers associated with the main executable.”
The goal of the Windows Mobile Application Verifier app is to test whether your app is stable and to detect common programming mistakes. It will assess the app's stability, pinpoint memory leaks, handle leaks, and some forms of heap corruption. It will attach to the app while said app is running and attempt to identify problems and issues that the developer may have overlooked.
