Upgrade Problem
Hi
I have yet another problem I'm hoping someone can help me with.
I have an in-house application that I have converted to an .msi using WPS, and this application includes a font called andalemo.ttf. The font is correctly entered into the font table, and installs fine.
I have also made this .msi upgrade previous versions (I have an older version of this app in .msi format as well),
When I tell my new msi to install on a computer that has the previous version installed, The install completes successfully, and it successfully removes the old version, but the font file is removed from windows.
For refernece, My RemoveExistingProducts action is set at 1060, and runs before MigrateFeatureStates and InstallInitialise in the InstallExecuteSequence table.
Any ideas?
I have yet another problem I'm hoping someone can help me with.
I have an in-house application that I have converted to an .msi using WPS, and this application includes a font called andalemo.ttf. The font is correctly entered into the font table, and installs fine.
I have also made this .msi upgrade previous versions (I have an older version of this app in .msi format as well),
When I tell my new msi to install on a computer that has the previous version installed, The install completes successfully, and it successfully removes the old version, but the font file is removed from windows.
For refernece, My RemoveExistingProducts action is set at 1060, and runs before MigrateFeatureStates and InstallInitialise in the InstallExecuteSequence table.
Any ideas?
0 Comments
[ + ] Show comments
Answers (9)
Please log in to answer
Posted by:
anks_09
15 years ago
Hi Beefy66,
I can give you the reason why it is happening so.You have kept Removeexisitngproduct action after costFinalized.In older version of msi it installs the same name file in windows system32 and during the time of costing it check the file present on the build.Fonts file are version less file so nif same name file it find during costing of the applciation it want install it again.You can try by moving the remove existing product action just above FileCost action and check.I guess it will install the Font File this time.
Regards,
anks_09
I can give you the reason why it is happening so.You have kept Removeexisitngproduct action after costFinalized.In older version of msi it installs the same name file in windows system32 and during the time of costing it check the file present on the build.Fonts file are version less file so nif same name file it find during costing of the applciation it want install it again.You can try by moving the remove existing product action just above FileCost action and check.I guess it will install the Font File this time.
Regards,
anks_09
Posted by:
MSIPackager
15 years ago
Posted by:
beefy66
15 years ago
Hi,
When I do a repair, the font does reappear.
I do validate my packages. This app did have loads of warnings (ICE33), but only 1 Error about the RemoveExistingProducts action location. I have since moved it to after InstallValidate to get rid of this error. This has made no effect on the behaviour of this font though.
When I do a repair, the font does reappear.
I do validate my packages. This app did have loads of warnings (ICE33), but only 1 Error about the RemoveExistingProducts action location. I have since moved it to after InstallValidate to get rid of this error. This has made no effect on the behaviour of this font though.
Posted by:
MSIPackager
15 years ago
I had a similar problem with an upgrade one (well my packaged version of an app had a custom action to remove the manually installed version) and there were about 6 fonts which didnt go back down.
When I did a repair they would appear - so just ensure that your shortcut is advertised and the font file is the keypath in it's own component and it will get put back via self healing on first run.
Sorry I can't tell you why it's getting removed during the upgrade.. I tried a number of things but never got to the bottom of it and in the end the request was dropped because of licensing issues... I think I would have been happy with the self-healing solution though.
If you get the the bottom of it, please let us me as is was most odd... [:@]
Regards,
Rob.
When I did a repair they would appear - so just ensure that your shortcut is advertised and the font file is the keypath in it's own component and it will get put back via self healing on first run.
Sorry I can't tell you why it's getting removed during the upgrade.. I tried a number of things but never got to the bottom of it and in the end the request was dropped because of licensing issues... I think I would have been happy with the self-healing solution though.
If you get the the bottom of it, please let us me as is was most odd... [:@]
Regards,
Rob.
Posted by:
beefy66
15 years ago
Posted by:
anonymous_9363
15 years ago
Details on the RemoveExistingProducts action and its location can be found here http://msdn.microsoft.com/en-us/library/aa371197(VS.85).aspx
Posted by:
beefy66
15 years ago
Posted by:
anonymous_9363
15 years ago
I am aware of the msdn documentation, (its one of my best friends!), but I couldn't find anything to help me with this problem.Yes, my response was aimed at the wider audience and should have had the text 'Details on the RemoveExistingProducts action and its location can be found here'. I'v edited it so that it now does.
I'm glad that you're now all systems go. Good job.
Posted by:
anks_09
15 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.