6/2/2023 0 Comments Decompiler Installshield![]() There's no supported way to do this, but won't you have to examine the files related to each installer to figure out how to actually install them after extracting them? Assuming you can spend the time to figure out which command-line applies, here are some candidate parameters that normally allow you to extract an installation. So I am therefore looking for a more stable way. ![]() However there is no good way of knowing, just launching the exe and hoping it will extract and terminate orderly rather then displaying GUI dialogs doesn't seem like a good solution. I some InstallShield versions support /b or /extract_all. (It would probably be possible to deduce which InstallShield version a setup.exe is by looking at version resources of the exe-file. Otherwise, if a solution only works for some versions of InstallShield it would be a step on the way. ![]() (My plan is to use it in a back-office tool, so this must be done programmatically without any user interactions.) Is this possible? (Initial research seems to indicate it will fail.) If it is possible to have a generic solution, for all recent versions of InstallShield that would be best. I am trying to extract the file-contents of an InstallShield setup.exe-file. Not sure how legal it is or if it does what you want. If you search for 'Windows Installshield Decompiler V1.00 Beta' on google you'll find this sw. Here are several convenient decompilers intended for it: InstallShield X. Decompiling is the process of obtaining the source code of the program being.
0 Comments
Leave a Reply. |