This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- InstallscriptMSI and InstallScript project Confusion.
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 09, 2009
07:03 AM
InstallscriptMSI and InstallScript project Confusion.
I have worked in both installscript and installscriptMSI project.
Can anyone please tell me what is the difference between them.
I heard that in installscriptMSI project the project flow is handled by MSI and not by installscript.How to do this?
Please help me I m in big confusion.
Can anyone please tell me what is the difference between them.
I heard that in installscriptMSI project the project flow is handled by MSI and not by installscript.How to do this?
Please help me I m in big confusion.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 09, 2009
10:54 PM
In a "pure" InstallScript project, all phases of the installation (user interface, feature and component installation, and file transfer) are all handled by InstallShield technology (MSI plays NO part in the installation whatsoever).
In a Basic MSI project (I know you didn't ask about this, but it helps in understanding the InstallScript MSI if you understand the MSI project type), The entire installation is driven by the Windows Installer (Microsoft) technology--even if you use extensions provided by InstallShield (like running SQL scripts, IIS configuration, XML file changes, and additional custom action types [including InstallScript Custom Actions]--all of which are implemented the "MSI way").
In an InstallScript MSI project, the installation is driven by the InstallScript engine which presents the user interface (dialog boxes), and then when it comes time to install the product, the InstallScript engine invokes the MSI mechanism to carry out the transfer of features, components, and files. When that part is done, you're back to InstallScript to do any post-installation work that may need to be done.
I hope that helps.
In a Basic MSI project (I know you didn't ask about this, but it helps in understanding the InstallScript MSI if you understand the MSI project type), The entire installation is driven by the Windows Installer (Microsoft) technology--even if you use extensions provided by InstallShield (like running SQL scripts, IIS configuration, XML file changes, and additional custom action types [including InstallScript Custom Actions]--all of which are implemented the "MSI way").
In an InstallScript MSI project, the installation is driven by the InstallScript engine which presents the user interface (dialog boxes), and then when it comes time to install the product, the InstallScript engine invokes the MSI mechanism to carry out the transfer of features, components, and files. When that part is done, you're back to InstallScript to do any post-installation work that may need to be done.
I hope that helps.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 10, 2009
12:08 AM
You have cleared my all doubts. This is realy very helpful to understand then concepts.
Lots of thanks for your reply.
Lots of thanks for your reply.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)