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
- :
- SharedDLL by default
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
‎Jun 16, 2010
07:54 AM
SharedDLL by default
I'm curious... Can someone please tell me why IS always sets the "Shared" setting (msidbComponentAttributesSharedDllRefCount) when creating new components, by default?
Best practice would be using Windows Installer reference counting and to use the Windows reference counting only for legacy stuff
Best practice would be using Windows Installer reference counting and to use the Windows reference counting only for legacy stuff
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 16, 2010
11:00 AM
I believe it all comes down to guessing the worst case scenario. We have a lot of people using our product who don't pay as much attention to each and every setting as perhaps they should, so a bad default can wreak a lot of havoc.
Obviously if a component is correctly marked shared or not shared, things are great. But if an unshared component is marked shared, or a shared component is marked unshared, which can have the worse effect? I.e. is it worse to occasionally leave an unshared file behind, or to occasionally delete a shared file that something else relies on?
Obviously if a component is correctly marked shared or not shared, things are great. But if an unshared component is marked shared, or a shared component is marked unshared, which can have the worse effect? I.e. is it worse to occasionally leave an unshared file behind, or to occasionally delete a shared file that something else relies on?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 01, 2012
08:51 AM
Ok ... just reactivating this old thread: How can I change the default behavior of IS2010 to set shared by default to No when adding new files?
And how to modify the behavior that at build time InstallShield sets shared to no when scanning for dependencies for these dependent components?
Thanks and regards,
Tobias
And how to modify the behavior that at build time InstallShield sets shared to no when scanning for dependencies for these dependent components?
Thanks and regards,
Tobias