PDA

View Full Version : Minor upgrade does absolutly nothing



mjanulaitis
07-20-2005, 10:33 PM
Minor upgrade does absolutly nothing??? If I recompile my binaries with a new version, then parse the ism file and specify a new version, then rebuild the installation, finally run the over install, the over install dialog displays, a few InstallShield wizard dialogs, but no files are updated, my services aren't stopped and restarted, my custom actions do run however. :mad:

Stefan Krueger
07-21-2005, 06:00 AM
As a first step, create a verbose log file to see what's happening.

Aravind
07-21-2005, 06:15 AM
Hi,

Did you change the product code and version number for the new product install??.

mjanulaitis
07-21-2005, 02:47 PM
The log file doesn't show any errors. I did not update any GUIDs. All I did was update my binary versions, parse the project file and update the version, and finally re-build. The process works for another project have have flawlessly. Not sure why this is happening with this project.

Aravind
07-21-2005, 11:59 PM
Hi ,

For minor upgrades,you have to change the product code & version no in the new install.then only the unstall work as you want..try the changes..

RChapel
07-22-2005, 02:00 AM
Hi,

you have to change the package code, product version, but the product code and the upgrade code must be similar for a minor upgrade as it's recommended in the help ("Major Upgrade vs. Minor Upgrade vs. Small Update")

@+

Stefan Krueger
07-22-2005, 05:36 AM
Could you post the update log?

sks2004
07-22-2005, 11:44 AM
I am experiencing the same results...I changed all/most of our versioned files -version values...then built a new release. I created a Patch, ran the patch successfully on the target machine. None of the files (about 40 files or so)changed to the new version. Nothing was altered.

Attached is my update log.

I have only recently begun investigating Patching...and I've discovered that I have a lot to learn, in a very short period of time.

sks2004
07-22-2005, 11:58 AM
BTW:
the previous version of the 40+ files = 2005.0.0.100
the latest version of the 40+ files = 2005.0.0.101

Stefan Krueger
07-25-2005, 06:26 AM
We would need a verbose MSI log created while you are applying the patch. This would list the reason why Windows Installer decided not to overwrite each file.

sks2004
07-25-2005, 01:31 PM
I found the problem; my fault ;) .
We have code that sets the Features to install...and this wasn't conditioned to ignore a Patch install (...And Not Patch).

Patching now works for me, as it should.