7 replies to this topic

[SOWI]

We added a new feature to our setup. The feature is required for our new software and therefore installed per default (InstallLevel 1).
During an minor update I have the problem that the new feature ist not intstalled. (Feature state is absent Requested state is null).

My question is what is the right way to force the installation of the new feature during a minor update??

Thanks
Frank

[Stefan Krueger]

There are basically two ways to do this (see also http://www.installsi...i/updates.htm):

a) Set the Remote Installation property of the new feature to "Favor Parent" and its Required property to yes.

b) Instead of REINSTALL=ALL use REINSTALL=ExistingFeature1,ExistingFeature2 ADDLOCAL=NewFeature

[SOWI]

Thanks for the quick reply but I still have problems with the solution:

Solution a)
The feature is not a child feature so "Favor Parent" is not available.
If I set the "Required" attribut the feature is still missing.

Solution :
I know that possibility but it requires a script or a command line interaction.
I would prefere a solution where the customer starts the setup and accepts the dialog box "Do you want to uprgade ..." (generated by setup.exe).

Is it possible to add a script action that performs the ADDLOCAL=NewFeature???

Thanks

[Stefan Krueger]

You could try using the AddLocal and Reinstall control events on the Next button of the Welcome dialog for instance.

[SOWI]

The problem is that I need a solution that works silent or with reducued user interface.

So I decided to do a major upgrade of the product. That works fine but now I have a problem to apply a minor/small on the installed major update!

Every time I try to do that a message box pops up that tells me that ".. another version of the product is already installed".
When I look inside the log file I see that the Seup.exe (generated by the InstallShield compiler) does not generate a command line

Command Line: REINSTALL=ALL REINSTALLMODE=vomus IS_MINOR_UPGRADE=1 ...

as it did during earlier updates of my product. What is wrong now??

I did a rollback to the last working version. But every time I changed the product code of my setup I'm no longer able to perform small/minor update on top of it.

I hope someone could help me.

[Stefan Krueger]

setup.exe should set that command line automatically, it doesn't have to be in the setup.ini (anymore). But you may need to use the setup.exe and setup.ini from the latest version (with the new product code)

[sebica79]

[SOWI]

After hours of investigations I found the reason for my problem!!

The installation used a diffrent product code during the major upgrade than my project file shows in its user interface. I scanned all my files for that GUID but I couldn't find any reference.

So I changed my project to the GUID that was used during the major upgrade.
Now my minor upgrades are installed as expected!