Testing Uninstallation Changes to an XML File
InstallShield 2020
Project:This information applies to the following project types:
| • | Basic MSI |
| • | DIM |
| • | InstallScript |
| • | InstallScript MSI |
| • | Merge Module |
| • | MSI Database |
| • | Transform |
After you have tested the XML file installation changes that you have configured through the XML File Changes view, you may want to test the XML file changes that occur during uninstallation. This enables you to determine whether the changes that you configured behave as you expected during uninstallation.
When you test the uninstallation changes, InstallShield uses the latest version of MSXML that you have on your machine to parse the XML file and execute the XPath expressions that you configured. When MSXML finds an area of the XML file that matches the XPath expression, the changes that were configured in the XML File Changes view are made.
Note:If your XML file changes include Windows Installer properties or InstallScript text substitutions, they are not replaced with the appropriate values during testing.
To test uninstallation changes to an XML file:
| 1. | In the View List under System Configuration, click XML File Changes. |
| 2. | In the XML Files explorer, right-click the XML file that you want to test and then click Test XML File Uninstall Changes. The Select Test XML File dialog box opens. |
| 3. | In the File name box, select the target file to which you want the uninstallation changes applied. |
The default value is the name of the file whose installation changes you last tested.
| 4. | Click Open. |
InstallShield applies the uninstallation changes that are configured in the XML File Changes view to the test file.
InstallShield displays details about the uninstallation test on the Results tab of the Output window. The details include a hyperlink to the test file. Note that if you have configured the XML file to be removed during uninstallation, the hyperlink may not work, since the file may no longer be present.
Tip:If the target file is open in a browser window when you perform the testing, you may need to refresh the browser window to see the test changes.
See Also