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
- :
- Re: Installscript and Merge Module
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
‎Jun 29, 2011
11:24 AM
Installscript and Merge Module
I have an installscript project and have added a merge module to a Feature. The merge module installs fine, but the installscript must set a property of the merge module - a license key.
I have tried MsiSetProperty() and get an error during compile for unknown function.
Can you use MsiSetProperty in a purely Installscript project?
Any help is appreciated. Thanks
I have tried MsiSetProperty() and get an error during compile for unknown function.
Can you use MsiSetProperty in a purely Installscript project?
Any help is appreciated. Thanks
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 29, 2011
03:10 PM
As a follow on - if I cannot use MsiSetProperty() how would I set a property in a merge module using Installscript?
I have tried FeatureSetTarget() and the function operates but does not seem to update the property for the merge module (.msm file). Perhaps the target media specified is wrong - I specified the Feature that the merge module is associated with.
I have tried FeatureSetTarget() and the function operates but does not seem to update the property for the merge module (.msm file). Perhaps the target media specified is wrong - I specified the Feature that the merge module is associated with.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 29, 2011
10:05 PM
I would not suggest using the Merge Module via the holder object (MMHO). Instead I would suggest building a Basic MSI project which consumes the merge module, and installing it and removing it through calls to LaunchApplication. You can then pass properties on the command line.
While the MMHO is convenient, the requirements that MSI places on installations are not well satisfied by its approach, so the MMHO has been deprecated.
While the MMHO is convenient, the requirements that MSI places on installations are not well satisfied by its approach, so the MMHO has been deprecated.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 30, 2011
05:38 AM
Thanks for the reply - I was wondering if either a Basic MSI or Installscript with MSI was a better approach.
My issue with that is that my Installscript project was an existing project and the msm was a new addition.
Short of getting the Premier addition (I have professional 2011) is their any way to easily convert an Installscript project to one of the other two, probably Installscript with MSI - assuming that works as well as Basic MSI with the merge module.
Or can I just start a new project and use the existing GUID to tag this project as the same as the previous? I want it to appear as the same project during install and uninstall so that installing the new will uninstall the old.
My issue with that is that my Installscript project was an existing project and the msm was a new addition.
Short of getting the Premier addition (I have professional 2011) is their any way to easily convert an Installscript project to one of the other two, probably Installscript with MSI - assuming that works as well as Basic MSI with the merge module.
Or can I just start a new project and use the existing GUID to tag this project as the same as the previous? I want it to appear as the same project during install and uninstall so that installing the new will uninstall the old.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 30, 2011
09:22 AM
Oh, you could migrate your whole project to Basic MSI (you'd have to perform a manual uninstall of the preceding InstallScript version), but I was just suggesting replacing the use of the merge module via MMHO to using it via an additional minimal Basic MSI project.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 30, 2011
10:15 AM
Oh okay - now I see where you were going - I will see about incorporating the msm into a basic msi project and then launching that installer from my installscript project.
Thanks
Thanks
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)