Cannot replace dll files ??
Hello everybody!
I've created a MSI database in order to replace some files.
Those files to be replaced are compressed as cab files and included in the
MSI database
Everything works fine for all kind of files except for "DLL" ones.
I have already tried to set the "Reinstall=amus" value in the PROPERTY
table.
Under the "components" menu I can see the DLL files and I've got the option
"never override" set to "NO".
The Always Overwrite option is not available to msi database...
Has anybody got any idea about how to replace those files? I have no need to
check any version information. I just want to replace them straight forward
every singl time.
Thanks.
I've created a MSI database in order to replace some files.
Those files to be replaced are compressed as cab files and included in the
MSI database
Everything works fine for all kind of files except for "DLL" ones.
I have already tried to set the "Reinstall=amus" value in the PROPERTY
table.
Under the "components" menu I can see the DLL files and I've got the option
"never override" set to "NO".
The Always Overwrite option is not available to msi database...
Has anybody got any idea about how to replace those files? I have no need to
check any version information. I just want to replace them straight forward
every singl time.
Thanks.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
anonymous_9363
14 years ago
Why are you using REINSTALL property? Notice the all upper-case usage, by the way - if you don't use that, the engine will ignore it, since you can only pass public properties - whose names are characterised by being all upper-case - on the command line. if you have updated the files then you should be building an update MSI.
I'd suggest a thorough reading of MSDN on updates/upgrades, in particular what you should do with ProductCode and UpgradeCode, etc. etc. You would to construct special handling if you want to ignore version numbering for DLLs (or indeed any file which contains file version information). Again, MSDN will tell all.
I'd suggest a thorough reading of MSDN on updates/upgrades, in particular what you should do with ProductCode and UpgradeCode, etc. etc. You would to construct special handling if you want to ignore version numbering for DLLs (or indeed any file which contains file version information). Again, MSDN will tell all.
Posted by:
chaparro
14 years ago
The default file versioning rules can be overridden or modified by using the REINSTALLMODE property. The installer uses the file versioning rules specified by the REINSTALLMODE property when installing, reinstalling, or repairing a file. The following example shows how the installer applies the default File Versioning Rules. The default value of the REINSTALLMODE property is "omus".
a Force all files to be reinstalled, regardless of checksum or version.If for that i make amus
I have read about this property to replace files...
Is not an update is only replace files in a directory... What is the good form to make this???
I edit the message-->
I have edit the "version" property in the FILE table. I have make more big version in the new dll and i think it works fine.
This is the good waY?
thanks
a Force all files to be reinstalled, regardless of checksum or version.If for that i make amus
I have read about this property to replace files...
Is not an update is only replace files in a directory... What is the good form to make this???
I edit the message-->
I have edit the "version" property in the FILE table. I have make more big version in the new dll and i think it works fine.
This is the good waY?
thanks
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.