Windows Installer Editor Reference
504
Wise Custom Actions
DiagnosticFileAssociationConflict
Processes the Extension table and checks the registry for support for each
extension. This test opens the registry key for the extension. If the key
exists, then the extension is already registered. The existing value of the key
is compared with the ProgId to be registered; if they match, the same
application re-registers the same extension. If they do not match, the
application being installed overwrites the existing extension. If the key is
empty, the extension is registered but no application is associated with it.
DiagnosticLaunchWeb
During Preflight Instrumentation, extracts URLs from the DisplayURL,
DownloadFile, and PostToHttp custom actions. It puts them in a table,
WiseUrlDiag, which is processed on the destination computer.
First, the test ensures that the connection can be opened to the specified
URL; then, the content is downloaded. The test then translates the result
into text.
DiagnosticManagedFileCheck
Ensures that files that have been distributed throughout the environment are
known and tested. This test ensures that a given computer is in a well
known, managed state and that testing and conflict management operations
are valid in the production environment.
DiagnosticMarkBeginRun
Indicates the beginning of the preflight test. Also determines if the
application that the preflight package is testing is already installed.
DiagnosticMarkEndRun
Indicates the end of the preflight test and that the .MSI was fully processed.
Preflight Analysis uses the DiagnosticMarkEndRun test to determine if a run
is incomplete.
DiagnosticOpenDocExtChec
During Preflight Instrumentation, builds a list of document extensions from
the OpenDocument custom action and saves the list in the WiseExtDiag
table. On the destination computer, checks the registry for support for each
extension.
This test tries to open the registry key associated with the extension. If it
successfully opens the key, then an association exists. Otherwise, no
association exists.
Diagnostic Payload Installed
Determines which files can be installed based on Windows installer file
versioning rules. The message it returns is: There are x files in this
installation, y files will be installed.
DiagnosticSecurityCheckFileRead
DiagnosticSecurityCheckFileWrite
DiagnosticSecurityCheckRegistry
Read
DiagnosticSecurityCheckRegistry
Write
Iterate through the files or registry keys and values that can be installed by
the installation and query the system for permissions to create, access, and
update files or values.
Build a list of all securable objects from the File and Registry tables. For
objects that exist, the test reads the security descriptor. For each profile on
the system (read tests) or the installer’s account (write tests), the test reads
each security descriptor’s access control list and determines the user’s level
of access to the object. For objects that do not exist (Example: objects that
will be installed), the parent object’s access control list is used to determine
the access level. The test also reads and applies information from the
LockPermissions table to gather additional security information (read test
only).
NalpLaunchCA
If you add Nalpeiron support to an installation, and you choose to add
support for Control Activation, this runs the Control Activation.exe after your
installation finishes on the destination computer.
Custom action
Description
