Last time I've checked, in 2003, this forum was strongly against "InstallScript MSI" projects in favor of "Basic MSI".
Here's a link to this discussion: http://forum.install...?showtopic=8734
Following advantages of "Basic MSI" were listed:
If you are not using InstallScript for custom actions you will not need to include the InstallScript engine in your setup. The installation of this engine is a frequent source of problems (famous 1607/1608 errors). The need to install the Installscript scripting engine has been eliminated in newer versions of Installshield. I believe scripts now run in a sandbox - sort of like Java - but with its engine included with the MSI. This applies to both Installscript MSI and Basic MSI with Installscript custom actions. This is a big improvement, but Installscript MSI is still discouraged, and Basic MSI recommended.
- It is standard and hence better for corporate deployment
- It is more light weight than standard
- It is less buggy
- Easier to debug/maintain and do not have to added complexity of Install Script.
- Major upgrade causes system changes to rollback. This issue had a knowledge base entry Q107649, but it seems I can no longer access it without login credentials. I don't know if the issue has been fixed.
- Should be used for corporate customers
The only disadvantage of "Basic MSI", as I see it, is a very steep learning curve.
QUESTION: has the situation improved now, 7 years later ?
What type of setup would you recommend now for corporate customers, "Basic MSI" or "InstallScript MSI" ?
Edited by Glytzhkof, 16 August 2014 - 16:44.