WiX 和 WiX 工具集有哪些限制？
我一直未能成功地尝试找到列出 WiX（Windows Installer XML）/WiX 工具集功能限制的文章或帖子。使用 WiX 几周后，我可以想到最新 RTM 版本 (v3.0) 中至少有两个限制：
- WiX Toolset 无法创建引导程序（安装程序.exe）。
- WiX 工具集无法从 COM 可执行文件检索COM 注册信息。
您还能想到其他限制吗？您在进行部署项目时遇到过什么情况吗？我认为这些信息对于学习 WiX 的人来说可能会很方便。
I have been unsuccessfully trying to find an article or post listing functional limitations of WiX (Windows Installer XML)/WiX Toolset. After using WiX for a couple of weeks, I can think of at least two limitations in the most recent RTM version (v3.0):
- WiX Toolset cannot make a bootstrapper (setup.exe).
- WiX Toolset cannot retrieve COM registration info from a COM executable.
Can you think of other limitations? Something you ran into while working on a deployment project? I think this info could be handy for people who learn WiX.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
对我来说，回答这个问题最简单的方法是 WiX 缺少 InstallShield 所具有的功能（功能差距）。
Bootstrapper/Chainer- WiX 有一个名为 Burn 的引导程序，现已包含在 WiX v3.6 中。写入而非读取 (AppSearch) XML
文件
具有读/写非模式
INI/XML 文件
和 MySQL
以编程方式更新/生成
项目。必须用原料来做这一切
XML。
没有本机 IIS 7 支持- WiX v3.5 Mostly Text Only 工具集提供本机 IIS7 支持重型起重设计师（参见
是WiX）。 XML 很简洁并且有它的特点
但它就像比较记事本
混合。
我已经使用热量相当成功地提取了 COM，所以这不再是我关心的问题。
It's easiest for me to answer this question in terms of what is WiX missing that InstallShield has ( feature gap ).
Bootstrapper/Chainer- WiX has a bootstrapper called Burn which is now included in WiX v3.6.writing not reading ( AppSearch ) XML
files
has patterns for reading/writing non
INI/XML files
and MySQL
programatically updating/generating
projects. Have to do it all with raw
XML.
No Native IIS 7 support- Native IIS7 support is present from WiX v3.5Designers for heavy lifting ( see
IsWiX ). XML is concise and has it's
place but it's like comparing Notepad
to Blend.
I've used heat to extract COM fairly successfully so that's no longer a concern to me.
我想补充几点，但这些很难被称为严重的限制，因为它们都可以解决：
再次让我重复一遍，我不考虑这些严重的限制。我对 Rob 和团队迄今为止所做的事情感到非常满意，他们正走在正确的轨道上！ :)
I would add several more points, but these can hardly be called serious limitations since they all can be worked around:
Again, let me repeat that I don't consider those serious limitations. I'm very happy with what Rob and the team have done so far, and they are on a right track! :)