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

You're reading from   WiX 3.6: A Developer's Guide to Windows Installer XML An all-in-one introduction to Windows Installer XML from the installer and beyond

Arrow left icon
Product type Paperback
Published in Dec 2012
Publisher Packt
ISBN-13 9781782160427
Length 488 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Toc

Table of Contents (23) Chapters Close

WiX 3.6: A Developer's Guide to Windows Installer XML
Credits
About the Author
About the Reviewers
www.PacktPub.com
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 14. Extending WiX 15. Bootstrapping Prerequisites with Burn 16. Customizing the Burn UI Index

Turning logging on during installation


If you get into trouble with your installer, it may help to run it with logging turned on. To do so, install your package from a command prompt using msiexec with the arguments /l*v, and the name of a file to write the log to. For example, if you had an installer called myInstaller.msi, you could use this command to write a log during the installation to a file called myLog.txt:

msiexec /i myInstaller.msi /l*v myLog.txt

Every event that occurs during installation will be recorded here. It works for uninstalls too. Simply use the /x argument instead of /i. The log can be pretty helpful, but also very verbose. If your installer fails midway through, you might try searching the log for the text return value 3. This indicates that an action returned a status of failure. Often, you'll also see a specific MSI error code. You can find its meaning by searching for that number in the MSI SDK Documentation help file that comes with WiX.

Note

You can also turn on logging for all MSI packages by editing the HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer key in the Windows Registry. This should be used with care though so as not to use too much disk space. See http://support.microsoft.com/kb/223300 for more information.

You have been reading a chapter from
WiX 3.6: A Developer's Guide to Windows Installer XML
Published in: Dec 2012
Publisher: Packt
ISBN-13: 9781782160427
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