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

The small update


A small update is like a minor upgrade except that it's usually smaller in scope. You might use it when only a few files have changed and you don't intend to change the Product element's version number.

The steps to create it are the same as when creating a minor upgrade patch with the exception of not changing the Product element's Version. They are as follows:

  1. Using Candle and Light, compile and link your original installer into a .wixout file.

  2. Make changes to your software's files and then create a second .wixout file. Do not change the Product element's Id or Version attribute.

  3. Make a Patch.wxs file and, using Candle and Light, compile and link it to create a .wixmsp file. Set the PatchFamily element's Version attribute so that this patch will be sequenced correctly related to other patches.

  4. Use Torch to create a .wixmst file that contains the differences between your two .wixout files.

  5. Use Pyro to combine the .wixmsp and .wixmst files into a final .msp patch file.

This gives...