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: A Developer's Guide to Windows Installer XML

You're reading from   WiX: A Developer's Guide to Windows Installer XML If you’re a developer needing to create installers for Microsoft Windows, then this book is essential. It’s a step-by-step tutorial that teaches you all you need to know about WiX: the professional way to produce a Windows installer package.

Arrow left icon
Product type Paperback
Published in Oct 2010
Publisher Packt
ISBN-13 9781849513722
Length 348 pages
Edition 1st Edition
Tools
Arrow right icon
Toc

Table of Contents (18) Chapters Close

WiX: A Developer's Guide to Windows Installer XML
Credits
About the Author
About the Reviewer
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

Reading from the Registry


To read data stored in the Registry, you'll use the RegistrySearch element. If the value you're looking for exists, it will be saved into a property you'll have placed as a parent element to the RegistrySearch. Here's an example that looks for the "myValue" value stored in HKEY_CURRENT_USER\Software\MyCompany and stores it in a property called REGISTRY_RESULT. Whichever property you decide to use, make sure that it is public (uppercase). The example follows:

<Property Id="REGISTRY_RESULT">
  <RegistrySearch Id="MyRegistrySearch" 
                  Root="HKCU" 
                  Key="Software\MyCompany" 
                  Name="myValue" 
                  Type="raw"  />
</Property>

By placing the RegistrySearch element inside a Property element, we're saying that we want the registry value to be stored in that property. The attributes on the RegistrySearch element mostly tell Windows Installer where to look for the value. Id just gives the search...

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