A question for Rob and the others who are responsible for the WiX architecture:
When using say a VBScript custom action (Type 6) with the BinaryKey attribute set (the VBScript is in the Binary table), why was it designed so that you HAVE to spcify a VBScriptCall attribute? The Windows Installer docs say that the function name is optional: Target The Target field of the CustomAction table contains an optional script function. Processing first sends the script for parsing and then calls the optional script function. But if I do not put the VBScriptCall attribute in I do not see how WiX will know that it is a type 6. It is not a big deal pragmatically, I am just wondering about the theory behind the decision. Is there something "wrong" with not having a Target specified in a type 6 custom action? - Brett ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
