两个组件都没有密钥文件时的文件版本控制规则 [英] File Versioning Rules When Neither Components Has a Key File
问题描述
根据我引用的URL，我了解Windows Installer使用密钥文件来比较组件的版本，日期和语言，并确定是否在目标计算机上更新组件.
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/zh-CN/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.
- 两个文件都有版本
- 两个文件都没有版本
- 两个文件都没有带有文件哈希检查的版本
- 一个文件具有版本
我不明白的是，如果两个组件都没有密钥文件，安装程序将如何确定是否需要更新组件?
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,
推荐答案
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.
这篇关于两个组件都没有密钥文件时的文件版本控制规则的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
