Have a vendor MSI (extrated from their setup). It has two exe files which need to be registered, as the MSI is not doing it.

Using Installshield, I can view the properties of the files, but self registration is greyed out.

Using Wise, I can get the files to register, but when I run the MSI, they don't shut down after registration, therfore stopping the install until they've been closed.

Once closing them, the install runs through and the app fucntions perfectly and as required.

Any quick ideas how to get around this?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Normally, COM-registering EXEs have a switch '/regserver' to perform just the registration. Are you running the EXE with this switch or just running it as-is?
Answered 11/09/2007 by: VBScab
Red Belt

Please log in to comment
At a dos promt, if I type the .exe name then /register the file registers and the app works perfectly. I need to do this post installation.

Is it best to maybe create a custom action which runs a VB script to do this? Just looking for the neatest way of doing it.

Answered 11/11/2007 by: Blue_Demon
Orange Senior Belt

Please log in to comment
You don't need to bother with a script. Just set the CA to run the installed EXE and add the switch. Having said that, for recalcitrant EXEs, I have a script which executes the relevant EXE with the switch and then checks that the relevant registry entries were created.
Answered 11/12/2007 by: VBScab
Red Belt

Please log in to comment