About a year ago I wrote some posts discussing the various InstallShield project types, and discussed the features and differences between InstallScript, InstallScript MSI, and Basic MSI projects. At that time, I had never used an InstallScript MSI project. Not once in the past 17 years of using InstallShield. I had always looked at InstallScript MSI as the ugly stepsister of InstallScript and Basic MSI.
Well, things have changed. I am finishing up a long project where I have been making major enhancements to an existing InstallScript MSI project for a client. Now, I’ve just decided that InstallScript MSI is not the ugly stepsister, but rather the middle child who gets no respect.
I think the project I have been on would have been a lot more difficult had it not had been scripted. If this had been a Basic MSI project, there would have been a hundred Custom Actions or more.
You never needed my approval in order to use an InstallScript MSI project, but now you have my opinion. For what it’s worth. If you have a huge installation that has a lot of custom code, it might just be the ideal situation to use InstallScript MSI.
Prevent Registry Entries from Being Deleted During Uninstall
