Creating new version of install/force uninstall of older ver

[neilnewton]

Hi,

I have two install files that was created in version 9. We have moved it version 12 but have made minimal changes to the two installs (we've only changes pointers to a couple of graphic files).

In the past, we have worked with our codebase and, to create a new version we have simply done a find replace on every version number in every file inside out .net solution code and recreated the install exe with the changed code. I did not create these installs and I am taking this, to some extent, on faith.It seems that this change to the version number cause the install to change it's guid and act as a new version of the install. What the meant from a practical point of view is that when this new version of the install is installed on a machine with the previous version, it automatically begins an uninstall of the old version.
As an example, say we have version 1.2. We test our code and recreate the build several times to allow a test of the code. It is still version 1.2 all this time no matter how many times we rebuild the install with installaware even though the code is being changed and test. If new install created for version 1.2 and installed over old version of 1.2, we are first shown the "modify, repair,uninstall" screen
Now we want to create a new version. We go to our .net code and do a find replace, changing the string that contains "1.2" (the version number) to 1.3. We build a new build with the new code. In the past if we installed a new install created with the 1.3 code on a machine that had the 1.2 version installed on it, installaware would always initiate an uninstall automatically upon seeing the different in version.

Some code has been changed, not on my watch, to deal with version numbers.Things have changed. Now when I try to replace on exisiting1.2 install with a new 1.3 install , instead of automatically starting an uninstall as in other build cycles, we are seeing the "modify, repair, uninstall" screen.

I will repeat some of this is taken on faith from people who created the original build but, from what I can see, the original scenario did work: changing the version numbers in the code and creating a new build that, any attempt to install the new install over the other one would intitiate an uninstall.

I have noticed there is a part of the installaware software called trialware and DRM. It "Seems'" to allow an explicty change in the guid number the current the version of the build. We have never used it but I'm wondering if createing a new guid for a new version of the build might cause the automatic uninstall functionality.

BAsically I am trying to find the fastest way to create a new "version" and cause installaware to "know" that a new version is being installed over a new version, causing an automic unintall. I apologize that my understanding of this is spotty since I've inherited. it. Any help would be appreciated.

Thanks,,
Neil

[FrancescoT]

Dear Neil,

I amy suggest you to have a look at the following post;
http://www.installaware.com/forum/viewtopic.php?p=727

The Meaning of Product and Revision Codes
The product/revision codes specified on the project options dialog are used by Windows Installer to uniquely identify your installation. If you author two installations that use the same product and revision codes, Windows Installer will treat both as installations of the same product. Therefore, pay attention to the following:

For different products, always use different product and revision codes. Whenever you generate a new project, InstallAware will automatically generate a new product and revision code for you.
For different versions of the same product, including product updates, you may use identical product codes, however you must use a different revision code. Having identical product codes but different revision codes between installer packages indicates that one of the packages is an upgrade.

Press SHIFT+CTRL+F11 to access Build Settings controls. If you wish to automatically update the revision code every time you build (excluding batch builds), check Change revision code automatically upon rebuild. This setting must be unchecked when debugging your setup. Checking it will enable seamless, automatic upgrades of your product.

Hope this helps you.

Regards