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
- :
- No MSI UI problem
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
‎Jan 22, 2010
07:53 AM
No MSI UI problem
I switched from InstallShield 2008 to InstallShield 2010. After upgrade I have problem with merge modules (standard Visual 2008 msm) included in my project. These msm-files do nothing if Display UI property of the corresponding Merge Module Holder Object set to "No MSI UI".
Everything work fine with MSI Full UI or MSI Basic UI.
Can anybody help with this problem ?
Everything work fine with MSI Full UI or MSI Basic UI.
Can anybody help with this problem ?
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 22, 2010
11:34 AM
In an InstallScript setup, I would tend towards launching the visual studio runtime redistributable. There are some tradeoffs to doing it this way, such as the lack of reference counting in the redistributable, but it's much easier to integrate into an InstallScript project.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 23, 2010
06:48 AM
Thanks for the reply. Does your advice means that there is a bug in InstallShield 2010 ? I didn't have such problem with InstallShield 2008.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 25, 2010
11:18 AM
That's a possibility, especially if you've confirmed you're using the same merge modules, and haven't made any other changes. If you want to try to debug it further, you could try setting the MSI Logging Policy to see if a verbose MSI log associated with the merge module holder object's installation tells you anything.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 28, 2010
09:20 AM
Same problem. We did a regular upgrade from IS 2009 to 2010. After migrating and building an existing 2009 project in IS 2010 we encountered problems with the installation of merge modules, they are not installed.
Changing the properties of the Merge Modules Holder Object from 'No Msi UI' to 'Msi basic UI' solves the problem, but this is not what we want. While installling there appearing 8 - 10 MSI screens with an progress bar.
The MSI logging policy which you mentioned in the previous comment is enabled by default in our testenviroment. There is NO log file, so i suppose the startparameters of MSIEXEC are wrong.
Is there a way to retrieve the used MSIEXEC command?
Changing the properties of the Merge Modules Holder Object from 'No Msi UI' to 'Msi basic UI' solves the problem, but this is not what we want. While installling there appearing 8 - 10 MSI screens with an progress bar.
The MSI logging policy which you mentioned in the previous comment is enabled by default in our testenviroment. There is NO log file, so i suppose the startparameters of MSIEXEC are wrong.
Is there a way to retrieve the used MSIEXEC command?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 28, 2010
01:27 PM
I can confirm that I have the same effect - I don't have LOG file in case of "NO MSI UI". I think that IS 2010 doesn't activate Windows Installer for installation of MSM-files. Why ?
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)