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

Installed state


While Windows Installer uses action state to determine if a feature or component should be installed, it uses the installed state to see if a feature or component has already been installed by a previous installation. In other words, does it currently exist on the computer?

Unlike the action state, the value of installed state can be used in feature and component conditions. For features, you'll prefix the feature's Id attribute with an exclamation mark (!), as shown:

!MainFeature = 3

For components, you'll use a question mark (?):

?ComponentA = 3

This allows you to include features and components based on whether they were installed before. You can also use them in custom actions and UI control conditions, such as to change which dialogs are displayed. Windows Installer uses this functionality itself, at least in regards to features, when you use the feature tree control. During a re-install, it will show the features as enabled that have been selected before and disables those...