Hello,
I'm using AI and doing setups since a couple of years.Now I found an unexpected behavior regarding the installation of a product.
Problem-Background: We have a product that sometimes need to be updated (we don't use Patch projects). We did always the changes in the project without changing the product code, only the "build number" of the product version, so that the user was instructed to uninstall the current version and to try again. But those users wanted the installation to uninstall older versions, so we changed the Product code to achive this but we got other behavior than expected.
Here the scenario (I use single numbers for GUIDs for simple reading):
- I create a project with Product Version""1.1.1.1", Product Code "1", Upgrade Code "2"
- I compile and install that setup
- I change the Product Code to "3", but let all the rest same (Upgrade Code "2", Version "1.1.1.1")
- I try to install the new setup (without uninstalling the other)
- At this point I would expect one of two things:
- The setup fails wiht a message like "Already installed", or "other version already installed"
- The setup uninstalls, i.e. updates, the current installed product.
Ok, I think we should maybe use a Patch project or something like that, or maybe I'm misunderstanding something here, so it would be great if you could help me understanding this. So here what we would like to do:
- The version number of the project (major, manor, and revision) should be the same in two or more different releases (background: an internal component gives actually the version number)
- The build number is the actual "setup-release" number
- When installing, if an older version if found, i.e. a smaller build number, it must be uninstalled first.
- If the last step is not possible, it should be avoided to install the product twice
Keneth
FOLLOW US
Get the latest news in Application Packaging