InstallAware

We have been happily using a script we developed that performs a transform install. Many of our users are able to run multiple versions on same machine; uninstall works perfectly.

The one issue we have always had was that an older version cannot be installed when a newer version is already installed. Towards the end of the installation progress we receive "Error" dialog, but no message indicating the underlying issue. This only occurs, as I say, when we try to install, for example version 1.1.0 and version 1.1.2 has already been installed.

Two questions:

* Is there a restriction (from WIS or otherwise) where transforms cannot go back in versions?
* If there is not a restriction, what are some the areas that I may look at to solve the problem we are seeing?

Thank you kindly,
Rjae

Are the upgrade codes between your projects the same?

See:
http://installaware.com/forum/viewtopic ... t=+upgrade

We have tried different upgrade codes as well different revision codes - as well as combinations of same/different between the two. We have not tried using a different product code...but as a last resort I suppose that will work.

It is my understanding based on debugging that once the Transform Instance statement is executed, the installation uses dynamically generated codes from then on. If that is (basically) true then I was thinking that changing the codes in project settings would have no affect on the underlying problem. (I am not saying I am correct, just sharing my thinking here.)

What is really suspicious is that we have no issues at all installing multiple versions of the product, as long as they increase in version number. Once the installation decreases in version number, we get the aforementioned error.

I wonder if there is a do-nothing product installer that InstallAware can run - one that uses Transform Install - to reproduce this scenario.

1. Install version 1.1.1 (should pass)
2. Insatll version 1.1.2 (should pass)
3. Install version 1.1.0 (should fail)

Ah, I see. I bet the upgrade code isn't being modified by the Transform Instance, which is causing this behavior. I should have a chance to investigate this tomorrow.

Your original comment was spot on. I have multiple branches I'm working on - and sadly I was changing the upgrade code in one branch, unknowingly building the project from another branch (command-line).

No need to test this. Thanks for the solution!