Re: [Installbase-devel] Using installbase to act as a frontend to setup.exe

[Damon C. <da...@yo...>]

> I'd like to use installbase to do two things:
> 
>     * Use it as a front end to run another setup.exe process, with the
>       proper parameters. I may also use it as a frontend to a number of
>       other setup.exe processes. Is this possible? How would I do that?
>     * I also want to use it to copy some specific files (i.e. a normal
>       install). Can I mix and match? I'm thinking I should but just in case.

    This is easily do-able.  The easiest way is to build the install
with the various setup.exe's added in file groups, then let the install
lay them down like normal.  Once they're done, you simply add
"External Program" install components for each setup you want to call.
Click the check box that says "Wait for program to complete" (or something
like that), which tells InstallBase to wait until that program finished
running before going on to the next component.

    If you don't actually want the setup.exe's to appear in the user's
install directory, you can set their destination directory to be <Temp>,
which is the temporary directory InstallBase uses during installation.
It gets cleaned up when the install finishes, so it would take your
other installations with it.

    InstallBase should then run each setup and wait for the previous
one to finish before going on to the next one.  You may have to play
around with it a bit, but I'm pretty sure that should get you where
you're going. 0-]

Thanks,

Damon