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: Basic MSI Project output a .MSI only
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
‎Oct 21, 2011
09:34 AM
Basic MSI Project output a .MSI only
Currently I am evaluating InstallShield 2012 and created a simple Basic MSI project.
It includes 2 files (both .NET assemblies) and I included three display languages. And nothing else. I don't have any prerequisites.
When building this project I always will get a setup.exe, and not an .msi. Even if in the releases view the "Create installation launcher (setup.exe)" option is turned off. I always get a setup.exe instead of the .msi file.
Also reducing the languages back to 1, doesn't seem to help.
How could I turn the creation of the bootstrapper/setup.exe off, like I could with InstallShield 12...
It includes 2 files (both .NET assemblies) and I included three display languages. And nothing else. I don't have any prerequisites.
When building this project I always will get a setup.exe, and not an .msi. Even if in the releases view the "Create installation launcher (setup.exe)" option is turned off. I always get a setup.exe instead of the .msi file.
Also reducing the languages back to 1, doesn't seem to help.
How could I turn the creation of the bootstrapper/setup.exe off, like I could with InstallShield 12...
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 21, 2011
10:01 AM
I believe this is a limitation of the evaluation version, it will only produce setup.exe.
I'm sure someone else will correect me if i'm wrong.
I'm sure someone else will correect me if i'm wrong.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Oct 21, 2011
10:04 AM
ncalverley is correct. Here's a KB article that explains the limitations:
Q200900: Functionality Notes for the Evaluation Version of InstallShield
Q200900: Functionality Notes for the Evaluation Version of InstallShield
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)