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

Collecting command-line arguments


To accept command-line arguments passed to your UI, use the Command.GetCommandLineArgs method, accessible via the BootstrapperApplication class. For example, we could add a method to our model class called GetCommandLine, like so:

public string[] GetCommandLine()
{
   return this.BootstrapperApplication.Command
      .GetCommandLineArgs();
}

Internally, this method will call the GetCommandLineArgs method, which returns an array of strings. Each index in the array will contain one of the arguments passed to the bootstrapper. If the user were then to pass an argument called "foo" to our executable, such as:

MyBootstrapper.exe /foo

Then /foo would be stored in the string array. Note, however, that the Burn engine intercepts some common command-line arguments and stores them in the Command object's Action property. We would use the Action property to access these arguments. For example, if the user passed /?, which is commonly known to be a request for a help...