3 replies to this topic

[hsong3]

hello everyone

i have a question about making a major and minor setup.exe file
i have done test so major and minor setup are working fine.

however, i need to make 1 setup.exe file to perform a minor and major depends on the client's version number.

how do i approach this issue??
do i need to make own custom actions to control this??

thank you

[Stefan Krueger]

If you populate the Upgrade table this should work. If the product code is the same as the existing version, a minor update should take place. If the product code is different, a major upgrade happens.

[hsong3]

Stefan, thank you for your reply.

however, do you mean a developer should decide whether to perform a minor or major during the designing time??
I want to have both options available so the decision can be made in runtime.

this is the situation that i am in now:

product #1

packagecode = A
productcode = B
Upgradecode = C

product #2 (this should perform the upgrade)

packagecode = D
productcode = E (but this will perform a major upgrade. if i keep this to B then this will do only minor upgrade. right??)
Upgradecode = C

thank you

[Stefan Krueger]

If the ProductCode of the old and the new product are the same, it's called "Minor Update".
If the ProductCode of the old and the new product are different, it's called "Major Upgrade".
The ProductCode is set by the setup developer at design time. Users cannot set it at runtime.
So this is a desgin time decision.

However there may be the following situation:
Product version 1.0
Product version 1.1, changed ProductCode
Product version 1.2, same ProductCode as version 1.1

Now version 1.2 would act as a minor update on computers where 1.1 is installed, but as a Major Upgrade on machines where 1.0 is installed.