/prexml and /postxml

Typically, an .inf file contains sufficient instructions to complete an installation, and CABWizSP translates those instructions into provisioning XML for the Configuration Manager to use. However, the /prexml and /postxml optional command-line flags for CABWizSP allow a developer to include XML that he or she created manually. Any acceptable configuration information can be added to the .cab file. For example, if the application has sufficient rights, it can send configuration information to the EMAIL Configuration Service Provider to change the current mail server. The /prexml and /postxml flags are also useful if the metabase needs to be updated during the installation of an application.

This XML must follow the appropriate Wireless Application Protocol (WAP) provisioning format as discussed in Provisioning Structure.

The /prexml flag adds a prexml file to the .cab file _setup.xml file before the instructions in the .inf file. The prexml file contains the full path and file name to a valid XML file that contains Smartphone provisioning XML that is ready by the Configuration Manager.

The /postxml flag adds a postxml file to the cab file _setup.xml file after the instructions in the .inf file. The postxml file contains the full path and file name to a valid XML file that contains Smartphone provisioning XML that is read by the Configuration Manager.

Warning   Do not enclose /prexml and /postxml in a top-level <wap-provisioningdoc> element; this element is produced automatically by CABWizSP.

The following diagram illustrates the layout of the _setup.xml provisioning document that is generated by CABWizSP. The /prexml and /postxml sections are optional.

For more information about XML provisioning of the Configuration Service Providers, see Configuration Service Providers.

See Also

Setup XML in .cab and .cpf Files | CABWizSP (SP Only)

Last updated on Friday, April 22, 2005

© 2005 Microsoft Corporation. All rights reserved.

Send feedback on this topic to the authors.