Hi All,

Though my application dosent have hkcu entry or any user specific data it self repairs in restricted user after i upgrade older version of the application.
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
Check event viewer as it should tell you why a repair was needed. Sounds like you have a problem with your update ;)

P
Answered 03/31/2008 by: Inabus
Second Degree Green Belt

Please log in to comment
0
Thanks for ur quick reply.I did that the component code is for the main .exe file to which shortcut is pointing.
Answered 03/31/2008 by: packengg
Orange Belt

Please log in to comment
0
Hi packenegg,
are we talking about an app of yours or a vendor MSI?
If you built it yourself: Has your main.exe a proper version info resource? If yes, did you update the version info in the File table?
If not, go and check the MSIFileHash table. If you create a new version of a file, you need need new hashes in there.
Hope, this gives you some ideas.
Regards, Nick
Answered 03/31/2008 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
Thanks All,

Finally issues is resolved .My package was unable to install one font file in installdir i made its attribute to Always overwrite by setting its vesion to highest value i.e 65535.0.0.0
Answered 04/01/2008 by: packengg
Orange Belt

Please log in to comment
0
Hope you don't need to author an upgrade with sequencing the RemoveExistingProducts action after the InstallFinalize action to update the file.
Answered 04/02/2008 by: AngelD
Red Belt

Please log in to comment
0
Hi packengg,
ORIGINAL: packengg
Finally issues is resolved .My package was unable to install one font file in installdir i made its attribute to Always overwrite by setting its vesion to highest value i.e 65535.0.0.0

Didn't even know that this can "work" like this!
IMHO, font files (format, ps or ttf doesn't matter) can't have a version resource included. How should Windows Installer detect the version then?
For unversioned files, you need to include a line in the MSIFileHash table, so WI can check the existing file against the hashes.
See: http://msdn2.microsoft.com/en-us/library/aa370107(VS.85).aspx
And especially this: http://blogs.msdn.com/astebner/archive/2005/08/30/458295.aspx
Hope this helps.
Regards, Nick
Answered 04/02/2008 by: nheim
Tenth Degree Black Belt

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