DuplicateParms=["]Action["] |
This determines what to do if a macro is found to use the same parameter name more than once.
Valid options are:
This could be useful if you have some default parameters that are added to the "end" of whatever the user provided removing the need to look for duplicates yourself. That way, if the user provides a value it overrides the default you set up.
This could be useful if you have some default parameters that are prepended to the "start" of whatever the user provided removing the need to look for duplicates yourself. That way, if the user provides a value it overrides the default you set up.
If not aborting then if a "/ConsoleFile" was specified some information will be written similar to:
[INFO] DUPLICATED MACRO PARAMETERS (Abort prevented: #option DuplicateParms=^USEFIRST^) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ NOTICE: The macro parameter "REMOVE" was specified more than once! WHERE : line 7 of "D:\TMP\TryMe.MM" #FIRST: `1` (type: V) #LAST : `2` (type: V)
Example |
The following examples shows 2 examples of the "REMOVE" parameter being used twice. No aborts will occur and in the second case "Different1" will be kept:
<$SomeMacro Key="INSTALLDIR" REMOVE="same" CHANGE="\" MAKE="Y" REMOVE="same"> #option DuplicateParms="UseFirst" <$SomeMacro Key="INSTALLDIR" REMOVE="Different1" CHANGE="\" MAKE="Y" REMOVE="Different2" REMOVE="Different3">