chrislynn5
Level 6

Install Level doesn't seem to work?

I have 13 features on a Basic MSI project. I can't get the install levels to work so that I can prevent certain features, etc from installing. I've tried everything. Help states that there are a few properties that affect this I have verified that none of those are set (The override of Install levels).
The INSTALLLEVEL is currently set for 100. The help guide says anything set with a number below that property will get installed. I set one feature as 101 and it STILL INSTALLS. I've tried many combinations.

None of these are set (taken from help):
The installation level specified by the INSTALLLEVEL property can be overridden by the following properties:


ADDLOCAL
ADDSOURCE
ADDDEFAULT
COMPADDLOCAL
COMPADDSOURCE
FILEADDLOCAL
FILEADDSOURCE
REMOVE
REINSTALL
ADVERTISE
Labels (1)
0 Kudos
4 Replies
chrislynn5
Level 6

well after trying many combinations it appears that that IS 2010 is just as buggy as it has ever been (back 10 years of use).
The only way I've been able to stop features is to leave the INSTALLLEVEL at 100 and set all features to 1, and 0 to NOT install. The documentation and forum responses all state INSTALLLEVEL and below will get installed. Well, setting INSTALLLEVEL to 100 and features to 105 doesn't work to prevent installation. Zero seems to be the only way to accomplish this.
And on top of that, the checkbox property is so screwy that I have to default the property to 1 (True) or no matter what condition I provide to set the feature to get installed the property is NEVER changed. Testing checkbox name doesn't work, only property works if ONLY set to 1 prior via the property table. So on the dialog the checkbox gets selected and I then require the user to uncheck (which I wanted start unchecked but doesn't work)!
0 Kudos
MattQVI
Level 8

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 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! 🙂
0 Kudos
MattQVI
Level 8

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.
0 Kudos
MattQVI
Level 8

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/dulvyizhihu...conditions.pdf
0 Kudos