Installshield project converters are disabled.How to enable them?

When I open an msi to convert that to an ism project in Installshield(tried in both 2014 and 2015 licensed versions).The options are disabled.


Please suggest me how to enable them and use these options.

0 Comments   [ + ] Show comments

Answers (2)

Posted by: anonymous_9363 7 years ago
Red Belt

From IS Help (my underlining):

"InstallScript MSI projects created using InstallShield, InstallShield DevStudio, or InstallShield Developer can be easily converted to the InstallScript project type"

The inference - and my experience - is that if the MSI wasn't created by IS, you can't covert it. Why would you want to, anyway? What do you need to do to the MSI that converting it to an ISM would be necessary?

  • We are creating an installer for a particular product and they have provided msi to us and machine where most of the path variables are corrupted with the ism.So that ism is useless now.

    Only working product we have is the previous msi which was created in installshield only.Now we need to convert it to ism so that we can use the old files and also include new dialog boxes.As we need to do this regularly for next versions to the same product, we are trying to convert as ism.

    Can you suggest anything more to try. - ur00361883 7 years ago
Posted by: anonymous_9363 7 years ago
Red Belt

>old files
Just do an admin install (msiexec /a...) and voilá! You have the source files.

>new dialogs
Either add them in to the MSI or, if you want to turn it into a project, start a new project, start capturing, "re-install" the app using the source files you just extracted, then add any registry junk you need.

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ