d(Session session)
> > {
> > return session.Features.Where(feature =>
> > !IgnoredFeatures.Contains(feature.Name)).All(feature =>
> > feature.RequestState != InstallState.Local);
> > }
> >
> >
> > On Mon, Sep 15, 2014 at 8:55 AM, Noel Farru
rrugia
> wrote:
>
> > I need to "access" MyFeature in the UserInterface code to make a condition
> > such that if no feature is selected for installation the "Next" button can
> > be disabled.
> >
> > Thanks and Regards,
> > Noel
>
e code to make a condition
> such that if no feature is selected for installation the "Next" button can
> be disabled.
>
> Thanks and Regards,
> Noel
>
> > From: jocoo...@jackhenry.com
> > To: wix-users@lists.sourceforge.net
> > Date: Mon, 15 Sep 2014 12:24:04 +00
te: Mon, 15 Sep 2014 12:24:04 +0000
> Subject: Re: [WiX-users] Check that at least one Feature is selected
>
> Currently, there is limited scoping of properties in Wix 3.x. The only
> problem you may sometimes run into is when a property crosses the UI to
> Execute boundary--to d
er 15, 2014 7:17 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Check that at least one Feature is selected
Hi all,
I have a setup with feature selection enabled like this one now, in a file
called "MyInstaller.wxs",
.
.
.
T
Hi all,
I have a setup with feature selection enabled like this one now, in a file
called "MyInstaller.wxs",
.
.
.
The code that handles the User interface is in another file called
UserInterface.wxi.
I know that to check if a certain feature is select
6 matches
Mail list logo