This is a basic MSI project. Is there any way to address this problem without changing the project type? ... View more

I think I have figured this out. Conditional levels are used when properties are defined in the property manager or set in the command line. For using dialog events to add/remove features one should use AddLocal/Remove. I just tried it and it works as expected. The case is closed. 🙂 ... View more

Hi Chad, Thank you for the prompt response. I tried to use this condition in the feature condition first. When this did not work, I tried component condition with the same result. When I use it in the feature condition, I specify Install Level: 1. To do that I add condition to the feature and set level:1 and condition INSTALLVS2010="YES". The package install level is 100. I tried both INSTALLVS2010="YES" and just "INSTALLVS2010" with the same result.It always evaluates to FALSE. As I pointed out before, if I assign a value to the condition in the Property Manager, then everything works as expected, but when I set the same property in a custom dialog, then it doesn't work. I have a feeling that the condition gets evaluated before the UI action with this dialog gets executed, but I don't know how to validate this assumption. The dialog is created after the standard "Customer Information" dialog in response to the "Next" button event. Is it to late to set a feature condition at this point? My goal is pretty simple: Install a feature based on a check box selection in a custom dialog. I am sure I am doing something wrong. Is there a right way to do it? Victor ... View more