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
- :
- how are the common dlls shared?
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 09, 2012
03:54 PM
Can't add a feature on Modify (change)
Basic MSI install.
I have 3 features. Core Files, Feature A and Feature B. My INSTALLLEVEL is 100 by default so that on a Custom install (_IsSetupTypeMin changed to Custom in the Property Manager) Features A & B have the big red X (don't install). This works.
If during the initial install, I say Feature A is installed it works. However, if I only install the Core Files then go to Modify (Change) and then say Feature A is installed NOTHING HAPPENS?!?!
What am I doing wrong here? Thanks in advance for any help/direction/words of wisdom! 🙂
I have 3 features. Core Files, Feature A and Feature B. My INSTALLLEVEL is 100 by default so that on a Custom install (_IsSetupTypeMin changed to Custom in the Property Manager) Features A & B have the big red X (don't install). This works.
If during the initial install, I say Feature A is installed it works. However, if I only install the Core Files then go to Modify (Change) and then say Feature A is installed NOTHING HAPPENS?!?!
What am I doing wrong here? Thanks in advance for any help/direction/words of wisdom! 🙂
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 21, 2012
08:20 AM
I got Feature A working properly (thanks to starting over and some assistance from tech support). It installs application for A and the common DLLs (shared by Feature B). However, on uninstall the common DLLs are left behind. Any reason why that is?
Also, based on the Feature... I have a self-extracting .EXE that is supposed to execute. But setting the condition to included INSTALLLEVEL=101 (Feature A) doesn't seem to work. The condition is always FALSE!
Thanks for your help.
Also, based on the Feature... I have a self-extracting .EXE that is supposed to execute. But setting the condition to included INSTALLLEVEL=101 (Feature A) doesn't seem to work. The condition is always FALSE!
Thanks for your help.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 21, 2012
09:43 AM
I was able to get the self-extracting .EXE to execute only when feature A is installed by using &[FeatureName]=3 in my condition. So, in my case &FeatureA=3 was used.
http://files.cnblogs.com/dulvyizhihua/installshield_conditions.pdf
Still don't know why the common DLLs are getting uninstalled/removed when Feature A is removed though.
http://files.cnblogs.com/dulvyizhihua/installshield_conditions.pdf
Still don't know why the common DLLs are getting uninstalled/removed when Feature A is removed though.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 27, 2012
04:14 AM
Hi,
did you put the common dlls inside components?
each dll in a separate component?
if true - are they marked a s shared components?
Or - are you using a merge module in order to install these common dlls?
Sharon.
did you put the common dlls inside components?
each dll in a separate component?
if true - are they marked a s shared components?
Or - are you using a merge module in order to install these common dlls?
Sharon.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 31, 2012
09:20 AM
Sharon,
Yes, I have the common DLLs in a single component that is (marked as shared) in both Feature A and Feature B.
Very limited (almost no) training in InstallShield so I am not sure about merge modules. Would this make it easier on me?
BTW, this wasn't a fresh .ISM file. I was taking an existing install and refactoring it to be feature-specific. Even though I separated the main .EXE for each feature into its own component it's almost like InstallShield still had it as part of the overall install in its noodle. Just what it appears like anyway.
Matt
Yes, I have the common DLLs in a single component that is (marked as shared) in both Feature A and Feature B.
Very limited (almost no) training in InstallShield so I am not sure about merge modules. Would this make it easier on me?
BTW, this wasn't a fresh .ISM file. I was taking an existing install and refactoring it to be feature-specific. Even though I separated the main .EXE for each feature into its own component it's almost like InstallShield still had it as part of the overall install in its noodle. Just what it appears like anyway.
Matt