Registering with Application Manager
To register an application with the Application Manager, call the Application Manager with the application's .ini file as a parameter. The command-line syntax for the Application Manager CeAppMgr.exe is as follows:
CEAppMgr.exe "CEAppMgr_ini_filename" ["CEAppMgr_ini_filename"]
- CEAppMgr_ini_filename
Full file name and path of the CEAppMgr .ini file for a single application. If the application has multiple components, you can run the Application Manager once with multiple .ini files, one file for each component.
One you call CEAppMgr.exe, the Application Manager completes the installation process. To add additional capabilities during the device installation process, use the Install_Init and Install_Exit functions. Because the installation procedure registers the application's .cab files with the Application Manager, a user can reinstall the application on the device at a later time or install the application on another device.
The full application name displayed in the CEAppMgr dialog box is extracted from the CAB Wizard .inf file. The extracted name is "provider appname". The value for provider is from [Version] Provider, while appname is from the [CEStrngs] AppName.
To remove an application from a Windows CE–based device, the user calls the Application Manager from the desktop computer. The Application Manager uses the information from the uninstall_name key in the .ini file to delete the application from the desktop computer and the Windows CE–based device. To add additional capabilities during the device removal process, use the Uninstall_Init and Uninstall_Exit functions.
For ActiveSync 4.0, Application Manager supports the /register flag. The /register flag allows you to register an application without immediately installing the application to the device. The following example shows how
CEAppMgr.exe /register "<path-to-1st-INI>" "<path-to-2nd-INI>"
CEAppMgr.exe /register "<path-to-3rd-INI>" "<path-to-4th-INI>"
CEAppMgr.exe
The first two calls register the application. The final call runs the Application Manager with the previous two applications available to download in the Application Manager UI. If the Application Manger is already active before you execute the code sample, then the registered applications automatically appear in the Application Manager UI.
See Also
Send Feedback on this topic to the authors