Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
WiX 3.6: A Developer's Guide to Windows Installer XML

You're reading from   WiX 3.6: A Developer's Guide to Windows Installer XML An all-in-one introduction to Windows Installer XML from the installer and beyond

Arrow left icon
Product type Paperback
Published in Dec 2012
Publisher Packt
ISBN-13 9781782160427
Length 488 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Toc

Table of Contents (23) Chapters Close

WiX 3.6: A Developer's Guide to Windows Installer XML
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Getting Started FREE CHAPTER 2. Creating Files and Directories 3. Putting Properties and AppSearch to Work 4. Improving Control with Launch Conditions and Installed States 5. Understanding the Installation Sequence 6. Adding a User Interface 7. Using UI Controls 8. Tapping into Control Events 9. Working from the Command Line 10. Accessing the Windows Registry 11. Controlling Windows Services 12. Localizing Your Installer 13. Upgrading and Patching 14. Extending WiX 15. Bootstrapping Prerequisites with Burn 16. Customizing the Burn UI 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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image