File Versioning Rules When Neither Components Has a Key File

为君一笑 提交于 2019-12-08 07:34:46

问题


According to URLs I referenced, I understand that the Windows Installer uses key files to compare the version, date, and language of components and determine whether to update the component on target machine.

http://msdn.microsoft.com/en-us/library/windows/desktop/aa368599%28v=vs.85%29.aspx http://msdn.microsoft.com/en-us/library/windows/desktop/aa371221%28v=vs.85%29.aspx

I also understand that default versining rules consist of 4 different cases as listed below.

  • Both Files Have a Version
  • Neither File Has a Version
  • Neither File Has a Version with File Hash Check
  • One File Has a Version

What I don't understand is that how does the installer determine whether the component needs to be updated if neither components has a key file?

And what's going to happen if neither components has a key file, but a file on the target computer indicates that its Modified date is later than the Create date? In this case, even when both products have a version, are they going to be considered as having Non-versioned files because no key file is set to components? How does the installer determine whether to install?

Any answers would be really appreciated,


回答1:


Every component from the installer must have a key member, this is imposed by Windows Installer to build a valid MSI package. Also, Microsoft strongly recommends that you create independent components for each DLL, EXE, OCX and hlp/help file. This will allow the file versioning rules to be correctly applied.



来源:https://stackoverflow.com/questions/18854897/file-versioning-rules-when-neither-components-has-a-key-file

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!