Book Image

WiX 3.6: A Developer's Guide to Windows Installer XML

Book Image

WiX 3.6: A Developer's Guide to Windows Installer XML

Overview of this book

The cryptic science of Windows Installer can seem far off from the practical task of simply getting something installed. Luckily, we have WiX to simplify the matter. WiX is an XML markup, distributed with an open-source compiler and linker, used to produce a Windows Installer package. It is used by Microsoft and by countless other companies around the world to simplify deployments. "WiX 3.6: A Developer's Guide to Windows Installer XML" promises a friendly welcome into the world of Windows Installer. Starting off with a simple, practical example and continuing on with increasingly advanced scenarios, the reader will have a well-rounded education by book's end. With the help of this book, you'll understand your installer better, create it in less time, and save money in the process. No one really wants to devote a lifetime to understanding how to create a hassle-free installer. Learn to build a sophisticated deployment solution targeting the Windows platform in no time with this hands-on practical guide. Here we speed you through the basics and zoom right into the advanced. You'll get comfortable with components, features, conditions and actions. By the end, you'll be boasting your latest deployment victories at the local pub. Once you've finished "WiX 3.6: A Developer's Guide to Windows Installer XML", you'll realize just how powerful and awesome an installer can really be.
Table of Contents (23 chapters)
WiX 3.6: A Developer's Guide to Windows Installer XML
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Chaining packages


You briefly saw that we use the Chain element to identify the MSI packages we'd like to install with our bootstrapper. However, MSIs aren't the only thing that can be referenced. The list may also contain patch files (MSPs), executables, and Microsoft updates (MSUs). Before getting to the specifics, let's take a look at the Chain element itself.

The Chain element

The Chain element enumerates the packages that you want to install together. This may include a suite of products that you'd like to install in one go, a single MSI with its prerequisites, or a group of patches, just to name a few possibilities. The packages are installed in the same order as they're listed in the markup. For example, here, Awesome1 is installed before Awesome2:

<Bundle ... >

   <Chain>
      <MsiPackage SourceFile="Awesome1.msi" />
      <MsiPackage SourceFile="Awesome2.msi" />
   </Chain>

You can change that order either by changing which element comes before the other...