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
- :
- component installed though its parent feature is not
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
‎Sep 04, 2009
04:19 AM
component installed though its parent feature is not
Hi all,
I have a Basic MSI project and the following installing log:
MSI (s) (54:5C) [11:41:46:892]: Feature: Synchronize; Installed: Absent; Request: Null; Action: Null
MSI (s) (54:5C) [11:41:46:908]: Component: CBTSynchronize; Installed: Absent; Request: Local; Action: Local
MSI (s) (54:5C) [11:41:46:908]: Component: CBTSynchronize.Download; Installed: Absent; Request: Null; Action: Null
MSI (s) (54:5C) [11:41:46:908]: Component: CBTSynchronize.Upload; Installed: Absent; Request: Null; Action: Null
All the three components are associated to that feature. Why is the first component installed? I'm installing custom features by adding in ISScript to ADDLOCAL property which seems to hold the right list of features before installing them.
Also, while looking in this log, I noticed these three components which I can't find in my IS project:
MSI (s) (54:5C) [11:41:46:892]: Component: __CBT.Binaries66; Installed: Null; Request: Local; Action: Local
MSI (s) (54:5C) [11:41:46:908]: Component: __CBT.ClientConfig65; Installed: Null; Request: Local; Action: Local
MSI (s) (54:5C) [11:41:46:908]: Component: __CBT.Binaries65; Installed: Null; Request: Local; Action: Local
I do have the components CBT.Binaries and CBT.ClientConfig and they are installing as expected:
MSI (s) (54:5C) [11:41:46:908]: Component: CBT.ClientConfig; Installed: Absent; Request: Local; Action: Local
MSI (s) (54:5C) [11:41:46:908]: Component: CBT.Binaries; Installed: Absent; Request: Local; Action: Local
Is anything to worry about?
I have a Basic MSI project and the following installing log:
MSI (s) (54:5C) [11:41:46:892]: Feature: Synchronize; Installed: Absent; Request: Null; Action: Null
MSI (s) (54:5C) [11:41:46:908]: Component: CBTSynchronize; Installed: Absent; Request: Local; Action: Local
MSI (s) (54:5C) [11:41:46:908]: Component: CBTSynchronize.Download; Installed: Absent; Request: Null; Action: Null
MSI (s) (54:5C) [11:41:46:908]: Component: CBTSynchronize.Upload; Installed: Absent; Request: Null; Action: Null
All the three components are associated to that feature. Why is the first component installed? I'm installing custom features by adding in ISScript to ADDLOCAL property which seems to hold the right list of features before installing them.
Also, while looking in this log, I noticed these three components which I can't find in my IS project:
MSI (s) (54:5C) [11:41:46:892]: Component: __CBT.Binaries66; Installed: Null; Request: Local; Action: Local
MSI (s) (54:5C) [11:41:46:908]: Component: __CBT.ClientConfig65; Installed: Null; Request: Local; Action: Local
MSI (s) (54:5C) [11:41:46:908]: Component: __CBT.Binaries65; Installed: Null; Request: Local; Action: Local
I do have the components CBT.Binaries and CBT.ClientConfig and they are installing as expected:
MSI (s) (54:5C) [11:41:46:908]: Component: CBT.ClientConfig; Installed: Absent; Request: Local; Action: Local
MSI (s) (54:5C) [11:41:46:908]: Component: CBT.Binaries; Installed: Absent; Request: Local; Action: Local
Is anything to worry about?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 05, 2009
10:53 AM
For your 2nd question, pls refer to http://blogs.msdn.com/windows_installer_team/archive/2005/08/18/451521.aspx
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 07, 2009
09:58 AM
I have discovered the cause of the problem: .NET scan at build.
Some .NET assemblies are used by several IS components, and even though they are copied locally for each component, the automatic search for dependencies installs all the other components using them, even if the parent feature is not selected. Setting .NET scan at build to "none" fixed it.
Those __CBT.xxx components are still present in the install log, though searching in the .ism project file I didn't find any reference to them.
much later edit: thank you, HenryL, I missed your answer when I replied to this thread!
Some .NET assemblies are used by several IS components, and even though they are copied locally for each component, the automatic search for dependencies installs all the other components using them, even if the parent feature is not selected. Setting .NET scan at build to "none" fixed it.
Those __CBT.xxx components are still present in the install log, though searching in the .ism project file I didn't find any reference to them.
much later edit: thank you, HenryL, I missed your answer when I replied to this thread!