AFAIK the DependencyExtension is about dependencies between installer packages.
I'm solving component dependencies with groups. Like this: <Component Id="A">...</Component> <Component Id="B">...</Component> <ComponentGroup Id="GroupA"> <ComponentRef Id="A" /> <ComponentRef Id="B" /> </ComponentGroup> <Feature> <ComponentGroupRef Id="GroupA" /> </Feature> So I'm only referencing groups in the feature and thus can add any dependency like any other component to that group. Regards Michael Am 08.11.2011 10:49, schrieb Steffen Henne: > Thanks for your answer. I actually think it's not necessary but we want to > try it out for the scenario the guy who creates our big main wxs file has > no idea about the dependencies between all the projects and we can define > them somerwhere else. > > I just found the DependencyExtension and tried to use it. Looks like this: > > in Feature A: > <Component Id="A" Guid="*"> > <dep:Provides Id="test" /> > <File Id.. /> > </Component> > > in Feature B: > <Component Id="B" Guid="**"> > <dep:Provides> > <dep:Requires Id="t" ProviderKey="test"/> > </dep:Provides> > <File Id.... /> > </Component> > > So B should be dependent of A right? > now if i build the installer and select only Feature B it says as expected > some dependencies are missing. > but if i now select feature A and B the same message pops up although all > dependencies are actually fulfilled. > > Any idea whats going wrong? > > > 2011/11/5 Blair Murri<os...@live.com> > >> If two components must be always be installed/removed together, I don't >> see why they can't be in all the same features. >> If one of the components depends on another but the dependency is not >> mutual, you could make a hidden feature that also contains the dependent >> component and use a custom action to enable that feature based on the >> depending component's action state. >> -Blair >> >>> Date: Fri, 4 Nov 2011 13:10:57 +0100 >>> From: steffen....@googlemail.com >>> To: wix-users@lists.sourceforge.net >>> Subject: [WiX-users] Dependencies between components >>> >>> Hi, >>> >>> I would like to define that one component can't be installed without the >>> other, without them being in the same feature. Is there any possibility >> to >>> define dependencies between components or component groups? >>> >>> or ist there any other approach to realise such a dependency? >>> >>> thanks in advance >>> >>> Steffen >>> >> ------------------------------------------------------------------------------ >>> RSA(R) Conference 2012 >>> Save $700 by Nov 18 >>> Register now >>> http://p.sf.net/sfu/rsa-sfdev2dev1 >>> _______________________________________________ >>> WiX-users mailing list >>> WiX-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> ------------------------------------------------------------------------------ >> RSA(R) Conference 2012 >> Save $700 by Nov 18 >> Register now >> http://p.sf.net/sfu/rsa-sfdev2dev1 >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> > ------------------------------------------------------------------------------ > RSA(R) Conference 2012 > Save $700 by Nov 18 > Register now > http://p.sf.net/sfu/rsa-sfdev2dev1 > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
