Copilot
Your everyday AI companion
Explore these results from Bing
    Upvotes4Top Answeranswered 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
    Was this helpful?
  1. 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 …

  2. People also ask
    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. The details here are with respect to InstallShield 2014.
    Setup does not hit custom action dll function. more info please see the image. The actions in your merge module are not being sequenced or otherwise invoked by the consuming msi. If you just added the custom action definition to the merge module, and did nothing special in the consuming msi, it doesn't know when to run these actions.
    Launches an executable file at the end of an installation. This is a Windows Installer DLL custom action. The name of the DLL file is SerialNumCAHelper.dll, and its entry point is LaunchProgram. Launches a readme file at the end of an installation. This is a Windows Installer DLL custom action.
    The entry points of your custom action DLL may not be what you think. By default, C++ "decorates" its function names. If you don't have a module definition file specifying their raw name, or an extern "C" applied to the function, they will be decorated. Try running dumpbin /exports customactions.dll to verify their names.
  3. Using Custom Action Return Codes To Exit The Setup

  4. The warning popup, "InstallShield DLL Custom Action: Failed