This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Calling Simple EXE
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 16, 2007
03:39 PM
how do i call a simple executable?
How do I call an executable from installshield?
I was trying several approaches.
i created a new custom action,
and then NEW EXE,
and i tried each of the 4 types,
and nothing happens.
it never runs my program.
perhaps i just don't have the sequence in the right spot.
i wish this wasn't so darn complicated.
I do not really want to deal with scripts,
and i found the launch... function, but don't quite know where to put that code. i thought the custom action seems like the right place to put it.
am i missing something simple?
thanks Jay
I was trying several approaches.
i created a new custom action,
and then NEW EXE,
and i tried each of the 4 types,
and nothing happens.
it never runs my program.
perhaps i just don't have the sequence in the right spot.
i wish this wasn't so darn complicated.
I do not really want to deal with scripts,
and i found the launch... function, but don't quite know where to put that code. i thought the custom action seems like the right place to put it.
am i missing something simple?
thanks Jay
(7) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 16, 2007
04:29 PM
The launch-an-EXE action type should do the trick; are you scheduling the action in one or both of the sequences? Is it an EXE you're installing, or one just for temporary use?
Running ICE validation on your MSI after building can help track down some issues with action scheduling, too.
Running ICE validation on your MSI after building can help track down some issues with action scheduling, too.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 16, 2007
04:45 PM
RobertDickau wrote:
The launch-an-EXE action type should do the trick; are you scheduling the action in one or both of the sequences? Is it an EXE you're installing, or one just for temporary use?
Running ICE validation on your MSI after building can help track down some issues with action scheduling, too.
specifically, i want to call another installer after my install is done. i was trying to run the quickbooks foundation class installer (QBFC4_0Installer.exe), which i include on my distribution. i also tried to include the quickbooks merge module which would be easier, but i'm not getting the right verison.
anyway, i just want to run that installer. can you give me the steps to do that?
i dont see "launch-an-exe" action type
under custom actions, i see NEW EXE, then 4 choices in how to find the EXE. not sure which one to use.
then what do i put for "install UI sequence" and "install exec seq"?
thanks
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 16, 2007
06:20 PM
One possibility is to create a "setup prerequisite"; it can install the other product before yours, if that's appropriate. You won't need to worry about sequences, with that.
Otherwise, it might be worth experimenting with a simpler executable, such as Notepad.exe. In general, actions that touch the target system should be scheduled for deferred execution in the Execute sequence, but if the other installer is also MSI-based, that's a problem since only one MSI Execute sequence can run at the same time.
(You'll generally also want to give the action a condition such as "Not Installed" to ensure it runs only during the initial install and not uninstallation, but first things first.)
Otherwise, it might be worth experimenting with a simpler executable, such as Notepad.exe. In general, actions that touch the target system should be scheduled for deferred execution in the Execute sequence, but if the other installer is also MSI-based, that's a problem since only one MSI Execute sequence can run at the same time.
(You'll generally also want to give the action a condition such as "Not Installed" to ensure it runs only during the initial install and not uninstallation, but first things first.)
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 18, 2007
05:39 PM
i dont want a prereq because the program doesnt get installed until after the first installation.
it's more like a followup to the installation.
and since it also uses installshield,
then i guess it has to wait until after the first installation.
so how do i queue it up to run after my installation?
how did installshield get to install .net installer an also sqlexpress during my installation??
doesnts make sense why this should be any different.
the purpose of this is to make the job of the enduser easier, not give him more steps to do.
it's more like a followup to the installation.
and since it also uses installshield,
then i guess it has to wait until after the first installation.
so how do i queue it up to run after my installation?
how did installshield get to install .net installer an also sqlexpress during my installation??
doesnts make sense why this should be any different.
the purpose of this is to make the job of the enduser easier, not give him more steps to do.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 19, 2007
12:33 PM
I believe .NET and SQL Express installers are implemented as setup prerequisites (setup.exe looks somewhere to see if they're already installed, and if not runs the appropriate redistributable before the main product).
Do you know if the other installer is MSI-based or not?
Do you know if the other installer is MSI-based or not?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 20, 2007
02:36 PM
Under 'Custom Actions' create a 'New EXE' (installed with product).
Sequence it after Install files as a deffered action if you want it to launch automatically, or simply tie it to a button event (I do something like this for SQLExpress install) for launching it.
Sequence it after Install files as a deffered action if you want it to launch automatically, or simply tie it to a button event (I do something like this for SQLExpress install) for launching it.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 22, 2008
02:41 PM
Hi,
I have a Basic MSI installer. How were you able to link you custom action that calls a simple EXE to a button?
Vhr
I have a Basic MSI installer. How were you able to link you custom action that calls a simple EXE to a button?
Vhr