Flexera Community

Feb 25, 2009

I have a basic MSI that is fully automated where there are no user dialogs presented. The MSI must decide on features to install based on current registry values.I have about 15 features in which all are disabled by default (install level 0) with th...

Feb 24, 2009

I am trying to add a feature condition to a basic MSI project. The condition is fairly long. There seems to be a limit on the length of the condition string, because when it gets to a certain length (not sure what it is), I get an error "An Invalid...

May 14, 2009

I think this is a bit off topic from the original post.Not sure if this is what you are looking for, but in your custom action vb script you can check to see if the feature is enabled. If it is enabled, then you can run your Web.Config XML modify co...

Feb 25, 2009

After I posted, I thought of that very same thing.I guess it would still be nice to have some way of doing it off of another feature install level as well. In my case it worked out ok to use the same condition from Feature_Y to set Feature_X to 0.I ...

Feb 25, 2009

I needed specific versions, so a range check was not possible. For now, I bit the bullet and reduced the length of all the properties so that I could get it to work.I guess the only thing I was not sure of is how multiple feature conditions are hand...

Feb 24, 2009

I could shorten the property names, but then I would have to go back and do that for all my other features that use these properties. A lot of extra work that I would like to avoid if possible.I was thinking about using multiple conditions for the f...

Flexera Community

User Statistics

User Activity

Disable feature install based on another feature (no UI Dialogs)

Feature Condition Max Length

Re: Disable feature install based on another feature (no UI Dialogs)

Re: Disable feature install based on another feature (no UI Dialogs)

Re: Feature Condition Max Length

Re: Feature Condition Max Length