Burn in WiX 3.6 如何将 MSI 文件捆绑到 .exe 中？
我有兴趣了解 WiX 如何捆绑使用 Burn 创建的 EXE 文件。我知道创建自解压 EXE 文件非常简单，我已经在 WinRAR。 EXE 文件解压到哪个目录，安装程序如何将该位置写入“添加/删除程序”？
另外，如何保留 UX 文件以供卸载？更有趣的是，升级过程中会发生什么？
I'm interested in knowing how WiX is bundling the EXE files created with Burn. I know that creating a self-extracting EXE file is pretty straightforward, having done it a million times in WinRAR. What directory is the EXE file being unpacked to, and how is the installation writing that location into Add/Remove Programs?
Also, how is the UX file being kept around for the uninstall? And even more interesting, what goes on during an upgrade?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
Burn 不会创建典型的“自解压 .exe”来解压内容然后启动。相反，它将所需的位（UX 或引导程序应用程序）提取到临时目录，然后在需要时缓存所需的包。这样，就不会浪费时间提取未使用的包。
缓存目录名为“Package Cache”并存储在 appdata 文件夹中，具体取决于它是每用户包还是每台计算机包。
升级没有什么特别之处，只是当一个捆绑包升级另一个捆绑包时，前一个捆绑包的缓存将被删除。
Burn doesn't create a typical "self-extracting .exe" that unpacks the contents then launches. Instead, it extracts the bits it needs (the UX or bootstrapper application) to a temporary directory and then caches the packages that are needed when they're needed. That way, no time is wasted extracting packages that aren't used.
The cache directory is named "Package Cache" and stored in an appdata folder, which one depending on whether it's a per-user or per-machine package.
There's nothing special about upgrades, except that when one bundle upgrades another, the previous bundle's cache is removed.