Attaching and running EXE files with MSI

[theseira]

Hello,

I am trying to create a simple MSI package that will allow me to run several smaller installer executable files. These installer EXE files have been and will be created using a separate installer utility, which by the way, does not have the ability to create MSI packages. So my goal is to use InstallAware to create a MSI package that includes all our installer files and to run each EXE file with some predefined parameters. Seems like a really straight forward process but it appears it is not that simple; not for me at least.

Hope my explanation makes sense.

Thanks.

[CandiceJones]

Its very simple! In the visual IDE, add each EXE to your setup under the Creatives view. then switch to the Run Programs view and run each of the added files from underneath $SUPPORTDIR$ at any time you like in your setup!

All visually possible, and you can switch to the MSIcode view if you want to customize this even further. The code will be automatically inserted for you in the MSIcode view and you'll be able to move it around anywhere you like

[theseira]

Please excuse my ignorance but where exactly in the IDE is the 'Creatives' view again? I read the manual and it does reference the 'Creatives' but it does not provide new users with the exact location of some of the visual components.

[theseira]

I think I got it. Creatives' are located in the Design view of the IDE. So the exact navigation would be, Design view > User Interface > Creatives.

[theseira]

I added my EXE files to the 'Creatives' menu and created new 'Run Programs' item. When I click the OK button, InstallAware poips up a dialog box asking me to make sure the 'Apply Install' command is added to my script. What script?

[theseira]

I figured it out but it is not intuitive.

[MichaelNesmith]

Like the IDE says, if you create new projects using the Quick Start wizard or one of the templates, the Apply Install command will be in the proper place.

I'm glad you were able to figure it out all on your own!

[theseira]

I am pretty close to getting my test project completed before I decide to purhcase one of the InstallAware versions. The problem I am experiecning right now is, I cannot register the OCX file I compressed in the MSI package. In searching a solution in your forum, I came across this post.

http://www.installaware.com/forum/viewt ... gister+ocx

I wanted to confirm if I require users to have Administrative priviliges to install my MSI by selecting the check box option, can I register my OCX component via the MSIcode section of InstallAware?

For example,

Register Library $TARGETDIR$\\myplugin.ocx

If so, does the above code go into the 'Process (Un) Installation [...] of the MSIcode section of InstallAware?

[CandiceJones]

Yes, you will need admin rights. And the right place for that code is right after Apply Install.

[theseira]

Where is 'Apply Install'? In the MSIcode section?

[MichaelNesmith]

Yes.

[theseira]

I am looking in the MSIcode section, where a user would enter scripts, and do not see any reference to 'Apply Install'. I may not be looking in the right place, because the only text I see in the section of the IDE are,

Check Application Requirements [...]

Check/Install Application Pre-Requisites [...]

Define Global Setup [...]

Setup User Interview [...]

Process (Un) Installation [...]

Finish Setup [...]

Any clues?

[MichaelNesmith]

Ever heard of code folding? You can expand these regions.

[theseira]

Got it. Thanks.

[theseira]

One more question. When I clicked on Build, IA is copying a ton of files from the Common Files folder and runtime files from teh InstallAware folder and placing them in the build folder. Can I stop it from behaving this way?