WiX 3.6中的Burn如何将MSI文件捆绑到.exe中? [英] How does Burn in WiX 3.6 bundle MSI files into an .exe?

查看:85
本文介绍了WiX 3.6中的Burn如何将MSI文件捆绑到.exe中?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我对了解WiX如何捆绑使用Burn创建的EXE文件感兴趣.我知道创建自解压EXE文件非常简单,已经在 WinRAR . EXE文件将解压缩到哪个目录,安装如何将该位置写入添加/删除程序"?

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?

此外,如何保留UX文件以进行卸载?更有趣的是,升级期间会发生什么?

Also, how is the UX file being kept around for the uninstall? And even more interesting, what goes on during an upgrade?

推荐答案

Burn不会创建将内容解包然后启动的典型自解压.exe".相反,它将所需的位(UX或引导程序应用程序)提取到临时目录中,然后在需要时缓存所需的程序包.这样,就不会浪费时间来提取不使用的软件包.

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.

该缓存目录名为"Package Cache",并存储在一个appdata文件夹中,该文件夹取决于它是按用户包还是按机器包.

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.

这篇关于WiX 3.6中的Burn如何将MSI文件捆绑到.exe中?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆