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 take the decision out of the hands of the end user and let you have the final say. Be warned that using feature conditions can completely remove a feature from a feature tree list. It may be better to use the ADDLOCAL property instead.

Towards the end, we discussed what action and installed state is. Action state can't be used in feature and component conditions like installed state can, but it can still come in handy in other types of conditions. Both come in very handy when it...