Legacy Update: Get back online, activate, and install updates on your legacy Windows PC

The Windows Mobile API Usage Tool performs static analysis of applications and binaries designed to run on Windows Mobile devices and reports on the usage of system APIs and other resources. The goal of the tool is to provide a report of system dependencies to the application developer, optionally including the deprecated APIs that the application may currently depend on.

Files

Status: Deleted This download is no longer available on microsoft.com. The downloads below are archives provided by the Internet Archive Wayback Machine from the Microsoft Download Center prior to July 2015.

No files found

File sizes and hashes are retrieved from the Wayback Machine’s indexes. They may not match the latest versions of files hosted on Microsoft servers.

The Windows Mobile API Usage Tool requires Microsoft Visual Studio 2005 or 2008.

The Windows Mobile API Usage Tool is a command-line utility that installs by default into the “Windows Mobile API Usage Tool” directory within the “Program Files” directory. The tool name is wmaut.exe, and when run without arguments or with incorrect arguments, a usage statement will be provided.

The tool takes as arguments a series of options, an output database used for reporting, and either an application (in .cab or .msi format) or a directory containing applications. If the output database file provided does not exist it will be created. If the database file does exist, you must either provide the /resume or /overwrite option as appropriate.

Additional advanced options are documented through the usage statement displayed by the tool.

If you wish to share the database file generated by the tool with the Windows Mobile application compatibility team, please email the database file (or for larger reports, a link to the file) to [email protected]. If you wish, you may use the /anonymize option to reduce the amount of application specific data (e.g. the application name) that is contained in the report(s). Use of the /anonymize option does not guarantee all application specific identifiable information will be removed.