New distribution build doesn't have the same GUID as previous build

[dbraas]

Hi

Using CVI 8.5.1 and it's integrated distribution builder, when i build twice the same application (with or without modifications between builds),
there's always a new GUID for the .msi file, despite the same one in the .cds file

I do need the same GUID to uninstall an old version prior installing the latest one.

Does anyone experience the same problem, or have any idea ?

[Mert_A.]

Have you actually tried upgrading an installed distribution? How are you determining that the GUID has changed? Are you certain that the UpgradeCode (not the ProductCode) has changed?

What is the version of Program Files\National Instruments\Shared\MDF\Bin\MDFCommon.dll on your system?

Mert A.
National Instruments

[dbraas]

Hi.

I've upgraded from 8.5.0 a few days ago. The first visible effect  : when i launch setup for the newest version, it doesn't uninstall the older one (previously installed).
To confirm this, i can simply show the .msi files properties and click on summary tab => advanced properties, i can see the GUID has changed.
Same info using orca on .msi file => View => Summary and look at package code.

If i change just this information with orca and paste the old GUID from previous version, setup will uninstall the previous version as excpected.


My C:\Program Files\National Instruments\Shared\MDF\Bin\MDFCommon.dll version is 2.5.1.92.

Regards,

David

[Mert_A.]

I have tested this (on a system upgraded from 8.5 to 8.5.1) and did not see a problem building distributions that upgrade each other.

It is expected that the package code changes every build. That is actually the defining characteristic of the package code. From an MSDN doc:

No two nonidentical .msi files should ever have the same package code.

If you are not seeing proper upgrading, I would first double check that your distribution's version number is 1) higher in the newer build of the distribution, and 2) being autoincremented on each build. Next I would use Orca to compare the UpgradeCode GUIDs (in the Properties table) of the two MSIs and ensure they are the same. Next, take a look at the Upgrade table. It should look like the attached screenshot (except with a different upgrade code and version numbers).

Are you ending up with two separate installations of your application? How do you know that the older installation is not being removed? Another very useful thing would be to get an installer log.  On a system that has an existing installation, try running a newer version of the distribution from the command line like this:

setup.exe /log installLog.txt

If you could post that log, along with the the new and old MSI files, I could probably figure out what the issue is.




Message Edited by Mert A. on 06-20-2008 11:15 AM

[dbraas]

Hi.

I re-checked an upgrade between two different builds and it seems that I was wrong on the first check.

Everything works just fine, the application is updated successfully, even if there's not the same GUID between builds. (Like old CVI installers)

I must apologise for the bad check.

Thanks for help !