(Windows Installer) 程序的不同版本在添加/删除程序中显示 2 个条目的原因是什么？
不知何故，我们最近部署的升级之一（内部部署，只有大约十几台机器左右）最终出现了问题，现在我们的程序有 2 个条目显示在 Windows 添加/删除程序中，我正在尝试找出可能导致此情况的原因。简而言之，Windows 使用什么来确定程序是替换以前的版本还是新程序？
我们正在使用 WiX 来创建安装程序，但 SVN 修订版中没有任何内容显示出太多异常（过去一年运行良好，有超过 100 次升级）。产品版本为*是因为我们每次都强制进行重大升级，但升级代码从未改变。
Somehow we ended up with something going wrong with one of our recently deployed upgrades (internal deploy, only about a dozen machines or so) and there are now 2 entries for our program showing up in windows add/remove program and I'm trying to figure out what could have caused this. In a nutshell what does windows use to determine whether a program is replacing a previous version or if it's a new program?
We are using WiX to create our installers, but nothing in the SVN revisions shows much out of the ordinary (been working fine for the past year with over 100 upgrades). Product version is * because we're forcing a major upgrade each time, but the upgrade code has never changed.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我相信Windows认为任何具有相同“次要版本”号的应用程序都是相同的，并且在安装新应用程序时会卸载具有相同“次要版本”的旧版本。编号约定的工作原理如下：
希望有帮助。以下是来自 MS 的一些资源：
http://msdn.microsoft.com/en -us/library/51ket42z.aspx
http ://msdn.microsoft.com/en-us/library/aa368032(VS.85).aspx
I believe that the Windows considers any applications with the same "Minor Version" number to be the same, and will uninstall an older version w/ the same "Minor Version" when installing a new application. The numbering convention works as follows:
Hopefully that helps. Here are some resources from MS:
http://msdn.microsoft.com/en-us/library/51ket42z.aspx
http://msdn.microsoft.com/en-us/library/aa368032(VS.85).aspx
当我的主要升级不包含或删除以前版本中的文件时，我曾经遇到过这个问题。所以我的问题是，在两个版本之间，第一个版本是否有第二个版本没有的文件？这就是我要检查的内容。
I once had this issue when my major upgrade didn't contain or remove a file from the previous version. So my question would be, between the 2 versions hanging around did the first have a file that the second does not? That would be what I would check.
事实证明，问题在于版本号的[修订版]部分没有被检查，我们偶尔会有内部版本仅在[修订版]号上有所不同。
What turned out to be the issue was that the [revision] part of the version number isn't checked and we'd occasionally have internal releases that differed only in [revision] number.
我遇到升级无法正常工作的问题，因为安装已从每用户模式更改为每计算机模式。我不确定确切的原因是什么，但我认为这与正在使用的 WixUI 的更改有关。现在已经明确设定了。
I had an issue with upgrade not working because the install had changed from per-user mode to per-machine mode. I'm not sure what was the exact cause, but I think it had to do with changes to the WixUI that was being used. Now it's set explicitly.