This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Major Upgrade issue - baffeled...
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 18, 2008
05:00 PM
Major Upgrade issue - baffeled...
Okay I have a strange issue coming up that I can not seem to solve and would like to know if anyone has any suggestions I can try.
We have version 1.0 of our product close to releasing and we are working on our version 1.5 of the same product.
What I did was copy the install and updated it to build in the new files and updated the version number. Since this one is a major upgrade I authored a major upgrade in the Upgrades table so that it would perform a major upgrade over all earlier versions.
I then installed version 1.0 on my machine and ran my 1.5 installled. I watches as all the files/folders/icons from the previous version were correctly uninstalled. It this proceeded to install the new files on to the machine. It all seemed to be okay, but then I noticed a bunch of files/folders were missing.
I then launched IE and automatically I get the version 1.5 install launching in repair mode. All the files/folder were then repaired and everything was installed correctly.
What I would like to figure out is why the files/folder were not installed, but were known by the install enough to perform a repair to re-install those files.
What is causing this and what can I do so that a proper major upgrade work and all files correctly installed?
Thanks for any help....
We have version 1.0 of our product close to releasing and we are working on our version 1.5 of the same product.
What I did was copy the install and updated it to build in the new files and updated the version number. Since this one is a major upgrade I authored a major upgrade in the Upgrades table so that it would perform a major upgrade over all earlier versions.
I then installed version 1.0 on my machine and ran my 1.5 installled. I watches as all the files/folders/icons from the previous version were correctly uninstalled. It this proceeded to install the new files on to the machine. It all seemed to be okay, but then I noticed a bunch of files/folders were missing.
I then launched IE and automatically I get the version 1.5 install launching in repair mode. All the files/folder were then repaired and everything was installed correctly.
What I would like to figure out is why the files/folder were not installed, but were known by the install enough to perform a repair to re-install those files.
What is causing this and what can I do so that a proper major upgrade work and all files correctly installed?
Thanks for any help....
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 19, 2008
07:14 AM
Did you change the product code in the new project?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 19, 2008
07:42 AM
Yes I changed the product code a few times and still same files/folder will not install.
Now I have to try another thing, but the original version 1.0 was created in IS 2008 and version 1.5 was updated and built with 1.5. I do not think that this should affect it, but I'll see if I simply update the 1.0 to 1.5, leaving it in IS 2008, and update the product code and test to see if that will perform the major upgrade completly then that will at least eliminate that possiblity.
Is there anything else that may cause this?
Thanks,
Now I have to try another thing, but the original version 1.0 was created in IS 2008 and version 1.5 was updated and built with 1.5. I do not think that this should affect it, but I'll see if I simply update the 1.0 to 1.5, leaving it in IS 2008, and update the product code and test to see if that will perform the major upgrade completly then that will at least eliminate that possiblity.
Is there anything else that may cause this?
Thanks,
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 19, 2008
03:36 PM
Okay I think I have this figure out. It seems that the key file version numbers of these components that are failing to install are actually higher than what is being installed.
So the install checks the version numbers of these key files and then marks the files as not to be installed, even though this is a major upgrade. So then the install uninstalls that previous version and installs the new version, skipping all the files that it marked as not to be installed. Once done then only a repair will put the files back onto the system.
I can fix most of these file versions, but some of just place holder files that only contains a version number that is not correct. Is there an easy way I could delete these files before the install does a install validations so that it does not record the file version? where in the custom actions can I place this so that it can delete the file before checking it's file version?
So the install checks the version numbers of these key files and then marks the files as not to be installed, even though this is a major upgrade. So then the install uninstalls that previous version and installs the new version, skipping all the files that it marked as not to be installed. Once done then only a repair will put the files back onto the system.
I can fix most of these file versions, but some of just place holder files that only contains a version number that is not correct. Is there an easy way I could delete these files before the install does a install validations so that it does not record the file version? where in the custom actions can I place this so that it can delete the file before checking it's file version?
