Build BUG - FeatureComponents table

[NassereB]

Hello,

I have a installer with multiple features and when selecting 1 feature then some files of another feature are also installed.

Example:
[CODE][InstallDir]
+ FeatureDirA
+ Bin
- File1
- File2
+ FeatureASubDir
- File3
+ FeatureDirB
+ Bin
- File4
- File5
+ FeatureBSubDir
- File6[/CODE]

Result after installing only FeatureA:
Hello,

I have a installer with multiple features and when selecting 1 feature then some files of another feature are also installed.

Example:
[CODE][InstallDir]
+ FeatureDirA
+ Bin
- File1
- File2
+ FeatureASubDir
- File3
+ FeatureDirB
+ Bin
- File4
- File5[/CODE]

Every component is set to only 1 feature! (Components appear once in FeatureComponents table)
When building the installer and opening the MSI that InstallShield created then File4 and File5 component appears twice in the FeatureComonents table.

Why does the buildproduce something very different?
What causes this and what can I do about it.

Many thanks,

NasB

[NassereB]

Is there no one that can help me.

It's a medium sized installer and I want to prevent recreating the installer from zero.

[joshstechnij]

Can you clarify what the problem is that you are seeing? You mention that components are all being associated to one feature, but the diagrams listed only show directories/files. If you go to the Setup Design view in your project, what does the feature/component tree look like?

[NassereB]

The feature/component tree for the given example:

FeatureA
- Component1 (File1 'target\subdirA\bin\assemblyA.dll')
- Component2 (File2 'target\subdirA\bin\assemblyB.dll')
- Component3 (File3 'target\subdirA\assemblyC.dll')
FeatureB
- Component4 (File4 'target\subdirB\bin\assemblyA.dll')
- Component5 (File5 'target\subdirB\bin\assemblyB.dll')
- Component6 (File6 'target\subdirB\assemblyD.dll')

After building the project and reopening it in direct mode it look like

FeatureA
- Component1 (File1)
- Component2 (File2)
- Component3 (File3)
- Component4 (File4)
- Component5 (File5)
FeatureB
- Component4 (File4)
- Component5 (File5)
- Component6 (File6)

Component 4 and 5 is now also listed in FeatureA

[joshstechnij]

Are any of the files contained in components 1, 2, and 3 .NET assemblies? If so, do these components have their .NET Scan at Build settings set to "Dependencies and Properties"? If any of these are set as such, does changing the settings to "Properties Only" change the behavior?

[NassereB]

Hello,

Thank you for you answer.

The files in components are .NET assemblies and all components are set by default to "Dependencies and Properties"

I have modified them to "properties Only" as you suggested. This solves my issue (Thanks a lot)

I just don't understand why InstallShield decides to add identical .net assemblies from other features/location.
Note that that building a release with the IS IDE produces another output than building a release with the IS Standalone Build.

Anyway, thanks a lot for your support.

NasB