Install Shield (remove old version and install new version)
We have an 'Basic MSI project' in install-shield 2015 version.
We are incrementing product version by 1 i.e. 1.0.75, 1.0.76 to 1.0.n
We want to remove earlier version when a new version is being installed of same product on same computer.
Install-shield mentions that it removes/uninstall earlier version only if major upgrade is done. Major upgrade means changing product code and we don't want that.
so suggest a way to uninstall older version as user runs the setup.
The product is developed in .Net 4.5.2 version
It has windows services and UI components.
We are incrementing product version by 1 i.e. 1.0.75, 1.0.76 to 1.0.n
We want to remove earlier version when a new version is being installed of same product on same computer.
Install-shield mentions that it removes/uninstall earlier version only if major upgrade is done. Major upgrade means changing product code and we don't want that.
so suggest a way to uninstall older version as user runs the setup.
The product is developed in .Net 4.5.2 version
It has windows services and UI components.
ASKER
But we do not want to change the major code version.
So there's a few different pieces in the installer.
There's your version number, 5.09.65 for example. That one you can change any part of it.
Theres the Product Code, which is a GUID that ppl wouldn't see. THAT guid needs to change.
And the Upgrade Code, another GUID that should never change.
Your numeric version you can bump only the minor parts.
But the product code GUID simply HAS to change. Thats it's sole purpose is to detect a newer pc of the same software.
There's your version number, 5.09.65 for example. That one you can change any part of it.
Theres the Product Code, which is a GUID that ppl wouldn't see. THAT guid needs to change.
And the Upgrade Code, another GUID that should never change.
Your numeric version you can bump only the minor parts.
But the product code GUID simply HAS to change. Thats it's sole purpose is to detect a newer pc of the same software.
ASKER
So I do not need to jump from 5.09.65 to 6.x.x. I could just make it 5.09.66
But the exact GUID is what must change and trigger the upgrade?
Alternatively, if the upgrade is not working, any chance to have it remove any previous version and have it install new one as part of install?
What you stated sounds like the best practice and common way of doing it? Sorry for lack of my knowledge.
But the exact GUID is what must change and trigger the upgrade?
Alternatively, if the upgrade is not working, any chance to have it remove any previous version and have it install new one as part of install?
What you stated sounds like the best practice and common way of doing it? Sorry for lack of my knowledge.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
we have two variety of same product light and pro. These comes with 32 and 64 bit, so we create total four setups.
If user install from light to pro or vice versa then we show messgae that existing serial key will not work with this product.
If we change product code when a new version (i.e. 2.0.76, 2.0.77) is released by us then how we will track which variety of product they have installed.
because their may be hundred versions with each having different product code. so we only change package code when a new version is released of a product.
If user install from light to pro or vice versa then we show messgae that existing serial key will not work with this product.
If we change product code when a new version (i.e. 2.0.76, 2.0.77) is released by us then how we will track which variety of product they have installed.
because their may be hundred versions with each having different product code. so we only change package code when a new version is released of a product.
ASKER
Any thoughts? :)
Sorry, somehow missed your update.
Okay, so how are you managing this NOW? If you already have a 32 and 64 bit, and a lite / full of each one, then you already have huge mix of installers, no?
I guess I'm just not quite understanding what the difference would be of changing the product code?
Okay, so how are you managing this NOW? If you already have a 32 and 64 bit, and a lite / full of each one, then you already have huge mix of installers, no?
I guess I'm just not quite understanding what the difference would be of changing the product code?
The Upgrade Code should remain consistent in all versions to link them together, but PC is intended to mark new versions.