I've got a MSI that is upgrading a previous version of the software which is also a MSI. I ran upgrade sync on the new MSI and added the old MSI upgrade code to the new MSI. When the new MSI is ran it installs the different files and then removes the old version. The problem I'm having is the uninstall of the old version is removing the INI files from the new verison. Has anyone ran into this and how do I fix it? I've got to have this done today and this is the only thing holding up the package.

I'm using Wise Package Studio 6.01.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
First thing that comes to my mind is that the component GUID of the components that contains the old and new ini-file is not the same. This is a clear symptom here.
When doing an upgrade like this, you have to be very careful about following the component rules.
If this is not an option here, you could move the SA "RemoveExistingProducts", and put it between the "InstallValidate" and "InstallInitialize" SA's. This way, the old application will be removed before the new one is installed. But this is not very efficient however, and thus not recommended.
Answered 04/18/2006 by: sikkert
Orange Senior Belt

Please log in to comment
0
The guids are different, I was hoping to not lose the efficiency of doing the uninstall at the end. I've had to do it before and I don't like it.
Answered 04/18/2006 by: CSummers
Senior Yellow Belt

Please log in to comment
0
Try to make the new GUID the same as the old one then. If the ini-files are different, then the file-versioning rules should take care of things.
Answered 04/19/2006 by: sikkert
Orange Senior Belt

Please log in to comment
0
Tried giving the component the same GUID and had the problem. To see if this problem is reproducable I just created 2 blank MSIs, created a INI file in both, and put the upgrade code of MSI1 into MSI2. When I install MSI2 it removes the INI and I'm left with nothing. Is this a bug in Wise or Windows Installer or am I not doing something right?

Can anyone see if they can reproduce this?
Answered 04/19/2006 by: CSummers
Senior Yellow Belt

Please log in to comment
0
CSummers: I can try it out later, if I have the time. But is the ini-file different between the original and upgrade? Is the original ini-file changed, after it is installed?
Answered 04/19/2006 by: sikkert
Orange Senior Belt

Please log in to comment
0
Hi!

I had the same problem with one of my applications.
I first maked the original package. Then I made upgrade #1 without problem.
But when I did the second upgrade the INI-file got removed on upgrade.
As far as I remeber, I didn't do any changes in the INI-file any of the times.

In my case I only needed to save one of the values, so I solved it by making a System Search to save the value in a Propery and then I used the property to set the value in the new file.

It would ofcouse be better if the INI-file was saved instead. =)

/Jonas
Answered 04/20/2006 by: jonasm
Blue Belt

Please log in to comment
0
Tried giving the component the same GUID and had the problem. To see if this problem is reproducable I just created 2 blank MSIs, created a INI file in both, and put the upgrade code of MSI1 into MSI2. When I install MSI2 it removes the INI and I'm left with nothing. Is this a bug in Wise or Windows Installer or am I not doing something right?

Can anyone see if they can reproduce this?


I just tried this now. Made 1 MSI whit an INI-file. Made a copy of this msi-file, and gave it a new name. Changed the ProductVersion and ProductCode properties since it is a major upgrade, changed PackageCode, made a change in the ini-file to verify it really being updated, and populated the Upgrade table, to remove the previous version.
Installed the first version and verified OK. Upgraded with the second file, and everything is OK, the INI-file is updated.

It seems to me there is something wrong in your package. Files being removed on an upgrade like this, is a typical example of wrong GUIDs on components. Have you tried the way I described above, making 1 package, then copying that and changing the mentioned properties?
Answered 04/20/2006 by: sikkert
Orange Senior Belt

Please log in to comment
Answer this question or Comment on this question for clarity