MAKEMSI quickly and reliably creates MSI files in a non-programmatic way\Source CodeCommandsMsiValFilter

---

The "MsiValFilter" Command

This command is used to to add to the MSI Validation filtering.

Note that if you upgrade "MSIVAL2" or its validation databases you may find some of the messages may have altered requiring you to update your filters.

Please read the "Don't ignore or completely turn off Validation Messages" section.

The macro takes these parameters:

• Filter Text (positional)
  This is the text we are searching for.

• Comment (optional)
  An optional comment which is generated into the filter file. It is used to provide a reason for the filter.

• Type (optional)
  Pass either "-" (the default) or "+". You should use "-" if it is OK if "MSIVAL2" generates this text (it will be filtered out) otherwise "+" if it is definately a problem (it will be filtered in).

• Re (optional)
  Is the "text" a regular expression (Y/N)? If "N" then a match will occur if a validation output line contains the "text".

• Case (optional)
  Do you want the match to be case (S)ensitive or (I)nsensitive (S/I)? The default is case sensitivity. Note that only "S" is supported for straight text (that is not a regular expression).

• Where (optional)
  The HTML report will contain location information but if its inside a macro it may be relatively meaningless, this allows you to add some details to the location info.

EXAMPLES

The following code creates a component with a "local_machine" keypath, this will generate 2 warnings however as we ensure that the MSI is always installed per-machine we will override the expected messages:

;--- Create component with HKLM (not HKCU) Keypath --------------------------
<$Component "LogShortcuts" Create="Y" Directory_="LOGDIR" LM="Y">
   ;--- Filter out validation messages cause by the above HKLM keypath ------
   <$MsiValFilter "Component LogShortcuts has non-advertised shortcuts. It's KeyPath registry key should fall under HKCU.">
   <$MsiValFilter "Component 'LogShortcuts' has both per-user and per-machine data with a per-machine KeyPath.">

   ;--- Create the shortcuts ------------------------------------------------
   <$DirectoryTree Key="LOGMENUDIR"    Dir="[ProgramMenuFolder]\Tool Logs" MAKE="Y" REMOVE="Y">
   <$Icon KEY="ViewLog.ico.exe" ".\ViewLog.ico">
   #(
       ;--- Create macro for log file shortcuts (all look the same) ---------
       #define ToolLogSc
       <$Shortcut
                   Dir="LOGMENUDIR"
                TARGET="[SystemFolder]notepad.exe"   ;;Non-advertised
             Arguments=^"[LOGDIR]{$#1}"^
                 Title="View {$#1}"
           Description="View the log file ({$Desc})."
                  Icon="ViewLog.ico.exe"
               WorkDir="INSTALLDIR"
       >
   #)
   <$ToolLogSc "FirstLog.log"   Desc=^Hold information of type 1^>
   <$ToolLogSc "SecondLog.log"  Desc=^Hold information of type 2^>
   <$ToolLogSc "ThirdLog.log"   Desc=^More stuff^>
<$/Component>

The following shows how a regular expression could be used to "turn off" the validation for all components:

<$MsiValFilter "Component .+ has non-advertised shortcuts\. It's KeyPath registry key should fall under HKCU\." RE="Y">
<$MsiValFilter "Component '.+' has both per-user and per-machine data with a per-machine KeyPath\."             RE="Y">

In the above:

• The regular expression characters ".+" match any one or more characters. The "dot" represents any character and the "+" following it means it matches one or more of these. Another very common sub-expression is ".*" which represents zero or more characters.

• The characters "\." represents a full stop, as it would normally represent "any character" it must be "escaped". In the case of a dot it wouldn't actually matter but not escaping brackets etc are a common reason for an expression to fail matching.

  If the regular expression is not working then you have probably forgotten to escape something, for example a bracket, that is you used "(" and not "\(".

Not that I recommend this but the last example shows how to ignore all warning messages (in fact any message containing that text):

<$MsiValFilter " WARNING ">

Please email me any feedback, additional information or corrections. See this page online (look for updates) MAKEMSI© is (C)opyright Dennis Bareis 2003-2008 (All rights reserved). Saturday May 28 2022 at 3:11pm Visit MAKEMSI's Home Page