MSP 不安装所有更新的文件
如果我有两个 MSI 包：
包 A) 2.0.1234 (initial_product.msi) packacge B) 2.0.2300 (updated_product.msi)
我可以在 installshield 中创建一个补丁，从这两个补丁生成一个 MSP，以将 2.0.1234 升级到 2.0.2300。奇怪的是，updated_product.msi 中的新文件没有安装。不过，正在更新的文件也会更新。新文件位于 AlwaysInstal 功能下。
它本质上会导致非标准安装，因为您丢失了新版本中的新文件，但您的旧文件正在使用较新版本的 DLL 进行更新。
什么会导致它们无法安装？ MSP 正在使用默认的 REINSTALLMODE=omus REINSTALL=ALL 运行，
谢谢
If i have two MSI packages:
package A) 2.0.1234 (initial_product.msi)
packacge B) 2.0.2300 (updated_product.msi)
I can create a patch in installshield that generates an MSP from the two to upgrade 2.0.1234 to 2.0.2300. What's strange is, the new files from updated_product.msi aren't getting installed. Files that are being updated get updated, though. The new files are under the AlwaysInstal feature.
It essentially results in a non-standard install, since you're missing new files from the new version, but your old files are getting updated with the newer version of the DLL's.
What would cause them to not be installed? the MSP is being ran with the default of REINSTALLMODE=omus REINSTALL=ALL
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
MSP 名称与原始名称不匹配的任何可能性（区分大小写！请参阅：http://msdn.microsoft.com/en-us/library/aa368060(v=VS.85).aspx ）？
Any chance that the MSP names don't match the original names (case sensitive counts! see: http://msdn.microsoft.com/en-us/library/aa368060(v=VS.85).aspx )?
本例中的问题是我没有使用根据以前的 MSI 文件对文件进行排序的选项。当您构建更新的 MSI 时，将其指向原始 MSI 非常重要，这样它就不会出现所有新的文件序列号。
（刚刚注意到我在过去几年中一直开放这个问题，并希望确保遇到这个问题的其他人都能找到这个问题的答案）
The problem in this case was I wasn't using the option to sequence the files based on a previous MSI file. When you build an updated MSI, it's important that you point it at the original so that it doesn't come up with all new file sequence numbers.
(Just noticed I had left this question open for the last couple years and wanted to make sure anyone else running into this issue can find the answer to this question)