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

Adding conditions to custom actions


After you've defined your custom actions and scheduled them into either InstallUISequence or InstallExecuteSequence, you have the option of adding conditions to them. These are added as the inner text of the Custom element and prevent the action from running if the condition is false. A common use for this is to only run the action during installation by using the NOT Installed condition.

<InstallExecuteSequence>
   <Custom Action="myCustomAction" After="InstallInitialize">
     NOT Installed
   </Custom>
</InstallExecuteSequence>

Other common conditions are Installed, which is true if the software is already installed, and REMOVE="ALL", which is true if the product is being uninstalled.

You can also use the action state and installed state of features and components or check the values of your custom properties. Look back to Chapter 4, Improving Control with Launch Conditions and Installed States, to review the discussion about these...