Rob,

You are right (or course) - it is reason 1. Below. If I leave the tag
empty (VBScriptCall="") it works as expected - the Target column in the
MSI is empty and it build cleanly. Should have thought to try it first -
I hate it when that happens.

Well, maybe that should be my sign to go home for the weekend...

- Brett

> -----Original Message-----
> From: Rob Mensching [mailto:[EMAIL PROTECTED] 
> Sent: Friday, April 27, 2007 2:45 PM
> To: Brett Kapilik; WiX-users@lists.sourceforge.net
> Subject: RE: Why are VBScriptCall/JScriptCall required?
> 
> One of two reasons:
> 
> 1.  The attribute that is required but may be empty.  It is 
> needed to differentiate the CustomAction element from one 
> custom action type to another.
> 
> 2.  It's a bug.
> 
> I'm pretty sure this is a case of the former not the latter.
> 
> Additionally, I'm seriously considering creating strongly 
> typed elements to aid authoring.  The CustomAction element is 
> high on the list.  The Condition element is up there as well.
> 
> 
> PS:  VBScript/JScript sucks for CustomActions 
> (http://blogs.msdn.com/robmen/archive/2004/05/20/136530.aspx).
> 
> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of 
> Brett Kapilik
> Sent: Friday, April 27, 2007 11:38 AM
> To: WiX-users@lists.sourceforge.net
> Subject: [WiX-users] Why are VBScriptCall/JScriptCall required?
> 
> 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
> 

-------------------------------------------------------------------------
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

Reply via email to