Version checking of files within a MSI-file
Hello,
I just create a .WSI file (via setup-capture) with Wise Package Studio 4.6 (and 5.1 evaluation).
When I use the resulting MSI, a newe vendor DLL file is overwritten with an older file.
After this another package that uses the same DLL won't work anymore.
My workaround is to replace all "old" DLLs, so the newe DLLs are compiled with the MSI.
I am looking for a general and easy way to enable the MSI t only to overwrite older files (checking for version and/or date).
I f you know answer PLEASE help me, if I don't solve this, I see myself rewrite every (re)package we use with an extra script to check for file version[:(].
TIA, Jem.
I just create a .WSI file (via setup-capture) with Wise Package Studio 4.6 (and 5.1 evaluation).
When I use the resulting MSI, a newe vendor DLL file is overwritten with an older file.
After this another package that uses the same DLL won't work anymore.
My workaround is to replace all "old" DLLs, so the newe DLLs are compiled with the MSI.
I am looking for a general and easy way to enable the MSI t only to overwrite older files (checking for version and/or date).
I f you know answer PLEASE help me, if I don't solve this, I see myself rewrite every (re)package we use with an extra script to check for file version[:(].
TIA, Jem.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
kkaminsk
20 years ago
If you have Wise and you did a repackage with it you can find some of the file info in the WiseVersionInfo table.
Posted by:
kkaminsk
20 years ago
Woah, I need more coffee!
What confuses me here is that MSIEXEC should only copy the newer file down if it is properly stamped with versioning information. What I would suggest is to try and use application isolation on the DLLs that are giving you an issue if in fact the MSI is writing out a bad version of the file. Still that means recompiling your MSIs. But it may be more simple for you to just recompile the MSIs with the version of the files you want.
What confuses me here is that MSIEXEC should only copy the newer file down if it is properly stamped with versioning information. What I would suggest is to try and use application isolation on the DLLs that are giving you an issue if in fact the MSI is writing out a bad version of the file. Still that means recompiling your MSIs. But it may be more simple for you to just recompile the MSIs with the version of the files you want.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
