Wix为整个树生成单个组件ID [英] Wix generate single component id for entire tree

问题描述

我是对wix几乎没有经验的人，并且我正在尝试为我负责的组件也支持Windows.我正在尝试为我的产品生成的一组文件创建合并模块.这些文件存在于许多子目录中.我想知道如何为整个树中的所有文件创建单个组件ID.我不担心较小的升级，因为这是我不会做的事情.我试图避免为每个文件生成大量GUID.

I am someone with little to no experience with wix and I am trying to support Windows also for the component I am responsible for. I am trying to create merge module for a set of files that my product generates. These files exist in numerous sub directories. I was wondering how I can create a single component ID for all the files in the entire tree. I am not worried about minor upgrades as that is something I am not going to be doing. I am trying to avoid generating numerous GUIDs for each of the file.

还有什么方法可以更改要安装文件的根目录的名称.当前，在我们的构建系统中，我要安装的文件最终位于目录名称"install"中.在由热量产生的wxs文件中，它作为安装出现.我想知道是否可以将其更改为实际的产品名称，而不是安装".

Also is there any way I can change the name of the root directory I want the files to be installed. Currently, in our build system the files I want to install end up in a directory name "install". In the wxs file generated by heat it comes up as install. I was wondering if I could change it to the actual product name instead of "install".

推荐答案

每个组件使用一个文件-这样可以避免各种问题(.NET程序集跨越多个文件除外).请参阅以下线程: Wix:一个每个组件一个文件还是每个组件几个文件?

Use one file per component - this avoids all sorts of problems (except .NET assemblies spanning multiple files). See the following thread: Wix: one file per component or several files per component?

Wix是用于创建安装程序的出色框架，但是学习曲线很陡.我强烈建议您阅读此出色的在线教程的几个部分: http://wix.tramontana.co.hu/.

Wix is a great framework for creating installers, but it has a steep learning curve. I strongly recommend you read a few sections of this great, online tutorial: http://wix.tramontana.co.hu/ .

如果您是基于样本的修补匠" ，则可以在本文中找到更快，基于样本的导览: http://www.codeproject.com/Tips/105638/A-quick-introduction-Create-an- MSI-installer-with

If you are a "sample based tinkerer", you can find an even quicker, sample based tour in this article: http://www.codeproject.com/Tips/105638/A-quick-introduction-Create-an-MSI-installer-with

Wix是动手的.仅关注示例，着重于创建组件和设置主要升级:

Wix is hands-on. Just focus on the samples, and focus on getting the components created and a major upgrade set up:

• 如何实施WiX安装程序升级? (现代便捷的方式)
• 如何使WiX主要升级正常工作?(传统方式-更灵活，更不方便)
• http://wixtoolset.org/documentation/manual/v3/howtos/updates/major_upgrade.html

• How to implement WiX installer upgrade? (modern, convenience way)
• How to get WiX major upgrade working? (legacy way - more flexible, less convenient)
• http://wixtoolset.org/documentation/manual/v3/howtos/updates/major_upgrade.html

一旦您了解了运行其余细节，就可以通过阅读文档了解所需的任何功能.结合使用Visual Studio/Votive和intellisense，可以确保您可以边学习边使用快捷方式，ini文件，xml文件，对话框等功能.

Once you got that running the rest of the details fall into place by reading the documentation for whatever feature you need. Using Visual Studio / Votive with intellisense ensures that you can learn as you go with features such as shortcuts, ini files, xml files, dialogs, etc...

另一个重要提示是使用 dark.exe (Wix工具包的一部分)反编译现有的MSI文件.这将生成带有代码的Wix XML，您可以将其复制并粘贴到自己的Wix文件中.我使用其他MSI工具来编译此类MSI文件，然后将所需的部分复制到Wix文件中-只是为了加快创建Wix XML的过程.研究反编译的XML非常有教育意义-可以节省时间.

Another top tip is to use dark.exe (part of the Wix toolkit) to decompile existing MSI files. This yields Wix XML with code you can copy and paste into your own Wix files. I use other MSI tools to compile such MSI files, and then copy the sections I need into my Wix file - just to speed up the process of creating the Wix XML. Studying the decompiled XML is very educational - a real time saver.

这篇关于Wix为整个树生成单个组件ID的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！