We have lots of problems with our MSI packages... so I'll try to ask this in an abstract way that doesn't target the actual validation of the package itself until it is determined that this behavior is due to our problems, and not a standard behavior with revving files.
Package A contains foo.dll, version 18.104.22.168. This package is installed on the target computer. The application is open and has locked the dll.
Package B has an older version of that dll, 22.214.171.124. When installing package B, it recognizes the version on the computer is older and does not prompt to close the application in order to replace it.
Package C has a newer version of that dll, 126.96.36.199. It correctly prompts to close the application in order to replace it.
Package D - the problem package - has version 188.8.131.52 as well. (Yes, I know this breaks a lot of rules...)
Why does MSI prompt to close the application in order to replace the exact same version? I would expect this to behave exactly like package B, not installing the dll but still increasing the reference counts.
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
installing dll of same version
1 reply to this topic