Thanks, I think this will fit when i get this working.
I tried:
But when I then only select the Symbols it still installs only the Symbols
ComponentGroup. Any idea whats wrong?
greetings Steffen
2011/11/8 Michael Stoll
> AFAIK you cannot do that with ComponentGroups.
>
> I
AFAIK you cannot do that with ComponentGroups.
If you like a flat structure you can do something like this:
...
This will install the "Binaries"-Feature when Debug or Binaries is
selected. It's like a dependency of "Debug" to "Binaries".
Regards Michael
Am 08.11.2011 12:39, schrieb
That perhaps explains the strange behavior of the DependencyExtension :D
Any possibibilty then to set one ComponentGroup as optional?
I'm thinking about having an ComponentGroup with Binaries and one with the
Program Debug Databases. Then the Debug dbs will be kind of addition to the
Binaries.
An
AFAIK the DependencyExtension is about dependencies between installer
packages.
I'm solving component dependencies with groups. Like this:
...
...
So I'm only referencing groups in the feature and thus can add any
dependency like any other component to that group.
Regards Michael
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
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 actio
6 matches
Mail list logo
