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: Compress all files into one .cab file vs. having one cab file per feature
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 21, 2010
07:40 PM
Compress all files into one .cab file vs. having one cab file per feature
Can someone explain to me What are the benefits of having .cab file per feature in Release Configuration?
Thanks.
Thanks.
(7) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 22, 2010
11:26 AM
The one place I can imagine it being truly advantageous is in downloadable MSIs - you can run msiexec /i http:///some.msi - as having separate cabs per feature allows unselected features' cabs to be omitted from download. To a limited extent, I could imagine trying to extend this to putting together disc images that omitted certain cabs, but that just seems risky.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 22, 2010
11:34 AM
Thanks for the reply Michael. I am working on an MSI project that contains of 9 Features. In Release Confuguration I have it to create one cab file per feature but after the build I end up with only 8 cab files. I am wondering what is happening to the 9th one. Any idea?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 22, 2010
11:46 AM
Does the last feature contain only components without files in them? If not, is it possible these files' components are also attached to other features? Either of these cases might leave the last cab with no data to include, so it wouldn't be generated. If neither apply, I'm out of easy ideas, and would probably need to reproduce the behavior.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 22, 2010
11:53 AM
Michael, the 9th feature does not have any empty component. It contains of 8 components that are shared with other Features and one component that is specific to this Feature.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 22, 2010
12:03 PM
Michael, one more thing that I wanted to add is that, this project used to make all the 9 cab files before. We moved Installshield on another machine and ran the build and one cab file is missing.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 25, 2010
05:02 PM
I removed the feature from the setup design and recreated it then reuilt and the problem is fixed!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 26, 2010
10:22 AM
Huh, I can't explain that. If you have a before and after version of the project file, it might be possible to track down any differences (using MsiDiff) to save time if this ever comes back. But I'm definitely glad you found a resolution!
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)