Symantec WINDOWS INSTALLER EDITOR 7.0 SP2 - REFERENCE FOR WISE INSTALLATION EXPRESS V1.0 Installation Manual page 494

Custom action
DiagnosticAppSearch
DiagnosticCheckDiskSpace
DiagnosticCheckDotNet
DiagnosticCheckExecuteLocally
DiagnosticCheckInUseFiles
DiagnosticCheckLaunchCondition
DiagnosticCheckPatchExistence
Windows Installer Editor Reference
Description
Enumerates the entries in the AppSearch table and evaluates the
expressions using the MSIEvaluate Property function. It then retrieves the
value of the property and reports the results.
Evaluates the disk costing and identifies computers that don't meet the
requirements. The MsiVerifyDiskSpace function calculates the costing and
validates the amount of disk space. The following properties are used to
display the amount of disk space required and available on the destination
computer:
PrimaryVolumePath
PrimaryVolumeSpaceAvailable
PrimaryVolumeSpaceRequired
PrimaryVolumeSpaceRemaining
Determines if .NET is required by this installation.
The Preflight Instrumentation determines if this check is required by
checking the MsiAssembly table for entries with 0 in the Attributes column. If
the check is not required, the Preflight Instrumentation does not insert this
check.
The test first ensures that there is a .NET assembly in the package. It then
retrieves from the registry the versions of .NET that are installed. If a
version of .NET is installed, it returns success and lists the versions installed.
If no version is installed the test fails. This check is inserted after the launch
condition check.
Evaluates type 34 or type 50 custom actions, which run a file that is
expected to exist on the destination computer. Once the test obtains the
application path and ensures that it is valid, it calls the load library to ensure
the application can be loaded and returns success if the application
succeeded, failure if not.
Tells the user how many files in the preflight installation are in use. The
message it returns is: Checked x files (OCX, EXE, and DLL files only), y are
in use.
Determines which launch conditions succeed and which fail. It enumerates
the LaunchCondition table and evaluates the condition using the
MsiEvaluateCondition API function.
During preflight instrumentation, Windows Installer Editor determines if any
actions were removed in the InstallExecuteSequence before the
LaunchCondition action. If actions were removed, Windows Installer Editor
cannot determine if the launch condition failed because of the removed
action or because of the condition. Preflight instrumentation sets the
property WISEDIAGLAUNCHWARN to 1 to indicate that Windows Installer
Editor cannot determine the reason the launch condition failed.
Based on the patch GUID, checks if the patch is already installed. If it is, it
returns a failure; otherwise, the test passes.
Wise Custom Actions
494