Introducing the Installer Cheat Sheet Series

Cheat sheets serve as great references, offering fast help in different areas of life. A great resource for our development team has been, which covers most major programming languages.

Recently, the Revenera team took the opportunity to develop cheat sheets for a few software installer related tasks to help you get your job done better and faster. Below are topics of the cheat sheets we will share with you throughout this series:

  • Common MSI Conditions
  • InstallScript Reference
  • Installer Folders

To kick off the series, the Common MSI Conditions Cheat Sheet gives you some of the most common conditions used in MSI projects for custom actions, features, components, etc. It also serves as a quick reference for most of what you need to know about Conditional Statement Syntax.

We invite you to offer suggestions for additional cheat sheets you’d like to see. Stay tuned to InstallTalk for the next cheat sheet coming soon.


5 comments on “Introducing the Installer Cheat Sheet Series

  1. Stefan Krueger on

    I believe there’s an error in condition “Feature installing or installed”. It should be:
    &FeatName = 3 OR (&FeatName 2 AND !FeatName=3)
    (while this is still ignoring Advertised and Run from Source).

    And I think the “64” doesn’t make sense in “XP 64”, “Server 2003 64” etc.

  2. Jenne Beauvais on

    Oh, how I wish this had been published years ago. Most of these our install group figured out over the years, but you have answered a couple of things that we’d never figured out. Thank you!

  3. Cary Roys on

    Arguably, the XP 64 and the 2003 64 doesn’t make sense as the Server conditions dosn’t check VersionNT64 (which would be how to differentiate between x86 and x64 Server).

    I guess it makes sense in context of comparing XP 64 against Server 2003 x64, though. Would you agree, Stefan?

  4. Stefan Krueger on

    MsiNTProductType tells the difference between a desktop OS (like Windows XP) and a server OS (like Windows Server 2003) – regardless of bitness. To check for bitness I’d recommend using the VersionNT64 property.


Leave a Reply

Your email address will not be published. Required fields are marked *