Bugs item #1340420, was opened at 2005-10-28 10:29 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1340420&group_id=105970
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: candle Group: v2.0 Status: Open Resolution: None Priority: 5 Submitted By: Riko Eksteen (rikoe) Assigned to: Nobody/Anonymous (nobody) Summary: Able to generate custom actions with invalid types Initial Comment: When I enter a custom action with the following settings: <CustomAction Id="MyAction" Execute="immediate" BinaryKey="myfile.exe" Return="check" /> the compiler doesn't give an error and generates a row in the CustomAction table with a Type value of 0, which is obviously not valid. Similarly, when I use just the FileKey attribute, a custom action row with type 16 is the result. Shouldn't the compiler give a warning if a FileKey or BinaryKey attribute is used without accompanying attributes like ExeCommand or DllEntry? Alternatively the type of custom action should be picked up from the extension of the file. I havn't checked all the possible combinations, but it is also possible to only specify the Directory attribute and generate a type "16" custom action... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=642714&aid=1340420&group_id=105970 ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today * Register for a JBoss Training Course Free Certification Exam for All Training Attendees Through End of 2005 Visit http://www.jboss.com/services/certification for more information _______________________________________________ WiX-devs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-devs
