Validation Suites (create CUB files) |
You can create your own MSI validations which you wish performed. These would probably be on top of those performed by "darice.cub" or another validation suite. If you just wish to make simplistic changes to an existing suite then you'd probably follow the "making changes to existing databases" approach.
As with other similar situations the VBS code is automatically syntax checked before being added to the ".CUB" file.
Please see the following sections:
USE THE GENERATED CUB FILE |
If you want to be able to use the validation suites you create in "ORCA" then you need to read the "Validation Suites + Orca Integration" section.
To use within MAKEMSI you can use the "VALID_MSIVAL2_DB" define to specify a specific validation suite which you would like to run as demonstrated:
#define VALID_MSIVAL2_DB \ D:\DBAREIS\Projects\Win32\MakeMsi\out\ICE.mm\Msi\DbValid.cub #include "DEPT.MMH" ;;Load MAKEMSI support
Note that for MAKEMSI to display validation results correctly after filtering no messages should be multiline (don't use "vbCRLF" etc).
Main Options |
;---------------------------------------------------------------------------- ;--- Options ---------------------------------------------------------------- ;---------------------------------------------------------------------------- #define? ICE_LOG_DIR <$MAKEMSI_VBSCA_DIR> #define? ICE_DEFAULT_SEQUENCE_RANGE 1-32767 ;;Use any "free" number starting at one #define? ICE_EXTRA_VBS_CONSTANTS #define? ICE_EXTRA_VBS_FUNCTIONS ;;Handy if you wish to add your own standard functions (in a header etc) #( '<?NewLine>' #define? ICE_FORCE_VARIABLE_DECLARATION_CODE option explicit #) #( '<?NewLine>' #define? ICE_DEBUG_CODE IceInfo("DEBUG: " & Text) #) #( '<?NewLine>' #define? ICE_TRAP_DISPLAY_MESSAGE IceFatal "TRAP: " & Text #) #( #define ICE_IceFatal ;--- Extra code to display error in a message box ----------------------- MsgBox {$TextVar}, vbCritical, "ICE ""{$IceName}"" Validation Problem" #)