Windows Installer Editor Reference
77
Working With Wise Installation Files
See also:
Tables Tab
on page 380
Saving an Installation as XML
You can save a copy of an installation (.WSI, .MSI, WSM, or .MSM) in XML format. This
lets you check the XML version of the installation into a text-based source code control
system (SCCS), use text-based file comparison tools to find changes, or perform
analyses with XML reporting tools.
You can set a global option in Wise Options to create an XML copy every time you save
an installation file, or you can export to an XML file on an as-needed basis. Depending
on the size of the installation file, creating an XML copy can take several minutes.
You cannot open an XML-format file in Windows Installer Editor.
To create an XML file during saves
Use this method when you plan to check the XML file into an SCCS from Windows
Installer Editor. This ensures that the XML copy is always synchronized with the original
installation file.
1. Select Tools menu > Options and click the General tab.
2. Mark the Create XML copy during save check box.
This global option causes an XML copy to be created every time you save an installation
file. The copy has the same name as the installation file with the extension .XML
appended, and it is saved in the same directory. (Example: If the current file name is
Application.wsi, the XML copy is named Application.wsi.xml.)
To export an XML file as needed
Use this method when you do not have an integrated SCCS, or to compare the version of
the installation you’re working in to the version that you checked out of your SCCS.
1. Select File menu > Export to XML.
2. In the Save As dialog box that appears, specify a file name with the extension .XML
and click Save.
If you have not named the installation file yet, name and save the installation file on
the Save As dialog box. When the Save As dialog box reappears, specify the .XML
file.
The current installation is saved and exported to XML format.
Working With Installations in the Software Manager
Database
There are restrictions on editing and saving an installation that has been added to the
Software Manager database (either by adding its meta data or importing it).
When the package path matches a package in the database
If you open an installation file and the Software Manager database contains a package
with the same package path, the application and package names on the Product Details