Summary

In this chapter, we talked about the meaning of launch conditions and how they can be used to prevent an install on a system that doesn't meet the minimum requirements you've set. When paired with AppSearch or the built-in Windows Installer properties, launch conditions are able to detect the operating system, .NET version, and whether or not required software is installed.

We touched on feature and component conditions and how they allow you to exclude a specific feature or component from the install. These conditions take the decision out of the hands of the end user and lets you have the final say. You saw that using feature conditions to set Level to 0 will completely remove a feature from a feature tree list. You may prefer to use the ADDLOCAL property instead or change the feature's level to a number higher than INSTALLLEVEL to disable it without hiding it.

Towards the end, we discussed what action and installed state is. An action state can't be used in feature and component...