Explore these results from Bing
- Viewed 3k times4answered Dec 7, 2012 at 13:12
Custom Actions only extract a single file to a temporary location under a temporary name. For the dependency on the .dll to work, they need to both be extracted, and at least the .dll must have the expected name. Typically this is easiest to do by adding both to "setup files" and referencing [SUPPORTDIR]\your.exe for the custom action.
Content Under CC-BY-SA license InstallShield Custom Action Reference - Revenera
See results only from docs.revenera.comUsing Custom Actions
InstallShield supports the use of custom actions to run InstallScript, VBScript, or …
DLL Custom Actions
If you need to perform an action in your installation that is not natively supported …
WEBDec 7, 2012 · I have a basic MSI InstallShield installation with a managed EXE custom action running from the Binary table. I tried a simple test that just runs a console and that works fine. When I add a .DLL assembly …
- Question & Answer
- People also ask
Using Custom Action Return Codes To Exit The Setup
The warning popup, "InstallShield DLL Custom Action: Failed