jaybird283
asked on
How to create a wrapper for an exsisting applicaiton installer
I am looking for an application that will allow me to create an exe (or msi) file that will kick off an OEM installer and pass some command lines to it or allow me to add some reg files. I have been able to do this with bat or vbs files but i would like to get away from doing that.
I have seen many installers that are exe files that really just call a msi file that has been encapsulated in the exe wrapper.
I thought that installshield did this but I can’t figure out how to do it.
I have seen many installers that are exe files that really just call a msi file that has been encapsulated in the exe wrapper.
I thought that installshield did this but I can’t figure out how to do it.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Note the drawback however. If you have installation OEMProduct, and you wrap it in MyWrapper, when the user installs it, he will have in his add/remove programs not OEMProduct but MyWrapper. Consequently, the user won't be able to do with OEMProduct the usual things that are possible with normal installation - such as add or remove features, repair, possibly even uninstall. So this is really should be used as last resort.
All the recommended methods (including the one found by the author) are appropriate for the purpose. If the author had some specific problems with any of them, he could ask. For deployment of setup.exe, zap file is the most appropriate because it does not require any other tools and does not wrap anything.
I suggest to split between
33479522
33502690
33649538
33649550
since those all allow wrapping existing setup.exe for deployment with parameters. The reason I did not include 33478389 and 33502511 is because they suggested tools to create new installation rather than "kick off an OEM installer and pass some command lines to it or allow me to add some reg files".
Strictly speaking, "add some reg files" excludes everything but 33479522 - winrar, winzip, and zap will launch the executable, but won't write anything into the registry.
33479522
33502690
33649538
33649550
since those all allow wrapping existing setup.exe for deployment with parameters. The reason I did not include 33478389 and 33502511 is because they suggested tools to create new installation rather than "kick off an OEM installer and pass some command lines to it or allow me to add some reg files".
Strictly speaking, "add some reg files" excludes everything but 33479522 - winrar, winzip, and zap will launch the executable, but won't write anything into the registry.
http://portableapps.com/news/2010-06-30_-_portableapps.com_launcher_2.0