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: Component's "Shared" Property
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
‎Aug 19, 2008
11:32 AM
Component's "Shared" Property
I am new to Basic MSI project types and just noticed that every component I created had the Shared property set to yes, even if the file is going into INSTALLDIR. Is this by design? Should every component be marked as shared? If not, can I change some setting in the IDE to default this setting to No which I believe should be the setting for 99% of my components.
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 20, 2008
07:35 AM
I believe that the IS IDE defaults to shared for new components (at least through IS12) and I have never been able to find a setting to change this default behavior.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 20, 2008
11:42 AM
yeah i've learnt to shut this off. If the refernce count somehow gets corrupted which for us is quite often, it may keep the older version of the files around and cause weird behaviour in your application.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 20, 2008
12:42 PM
Shared is a setting that you use if you think you are going to have multiple copies of those files. It defaults to yes so many of us have gotten use to turning it to no when adding components.
The windows installer keeps the count of shared files in the registry and that area can get very mucked up. And yes you'll end up leaving files behind on uninstall...
you can see the counts in your registry here:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\SharedDLLs
The windows installer keeps the count of shared files in the registry and that area can get very mucked up. And yes you'll end up leaving files behind on uninstall...
you can see the counts in your registry here:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\SharedDLLs
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 21, 2008
10:15 AM
I have not found a place to turn this off as well. It would be nice if InstallShield would expose this setting so that we can say we want to have all new components marked as NOT shared by default.
We have a standard bug ticket created for each new project that reminds us to go through the setup and verify that none of the components are marked as shared UNLESS they are supposed to be shared. Then we have to add to this ticket a list of the files that are supposed to be shared between applications.
We have a standard bug ticket created for each new project that reminds us to go through the setup and verify that none of the components are marked as shared UNLESS they are supposed to be shared. Then we have to add to this ticket a list of the files that are supposed to be shared between applications.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 21, 2008
11:00 AM
I agree. Having an option to turn this off would be nice. This would be similiar to the option to set the default for the ".Net Scan at Build" component property.
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)