Hi,
I would like to launch a custom action, MyFoo.exe. However, MyFoo.exe has a few dependencies, such as MyBar.dll and MyBaz.dll. MyBar.dll and MyBaz.dll must be present in the same working directory as MyFoo.exe in order for MyFoo.exe to execute. These dependencies cannot reside elsewhere in the PATH.
MyFoo.exe, MyBar.dll, and MyBaz.dll are not required for my software to run once it is installed, they are only required before/during an actual installation of my software. Because these files are not required by the actual end-software, I would like to execute MyFoo.exe as a custom action, without really deploying it as a normal file that is part of the actual installation.
An additional requirement that I have is to execute MyFoo.exe as early as possible in the install sequence. That is, before files are copied to the destination machine, etc.
Essentially, I think I need a "Add Attached Custom Action" -- but in this case the custom action in question, MyFoo.exe, has a few dependencies.
How can I execute a custom action, early in the install sequence, if it has some dependencies?
Thank you.
FOLLOW US
Get the latest news in Application Packaging