Application self repairs after upgrading.
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.
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
Answers (6)
Please log in to answer
Posted by:
Inabus
16 years ago
Posted by:
packengg
16 years ago
Posted by:
nheim
16 years ago
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
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
Posted by:
packengg
16 years ago
Posted by:
AngelD
16 years ago
Posted by:
nheim
16 years ago
Hi packengg,
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
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
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.