Hello everyone,
I wanted to run something by you all and ask for your help implementing
this. If this is not possible to do with build in functionality, or would
require running an outside script that is an option but not ideal.
Step One: Read a list of strings and dependencies in the form of r
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?
>
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
>>>
>>>> If two components must be always be i
gt; 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
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@
ate: 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 wit
e 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,
>
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
Ste
TA7YT0xO0Q9MTtTQ0w9MA==
> X-Message-Status: n:0
> X-SID-PRA: Stryder Crown
> X-SID-Result: Neutral
> X-Message-Info:
> JGTYoYF78jHzN0ggHigGvCDroLZzwBAF365lf6XoQ6Euhy1Ty6pmdKrUxjQ+QDmOyAzPAzICNKXLudAZXa2b6yPg11YDjHHN
> Received: from lists.sourceforge.net ([216.34.181.88]) by
&g
I'm using Visual Studio for these, which has proven to be a big help for
organizing everything. And I guess that's kinda the mentality I'm coming at
this with. Create a project for a major component, and then include
references to everything that is needed to run that. I sepecifically
_don't_ wa
1. I personally haven't sat down and thought about all of them.
Honestly, the strategies I use come from my days of working in C/C++.
WiX works very similarly. If you organize your code well in C/C++ and
follow similar organization efforts in WiX, it all works out.
Duplicating code across .lib
Do you have any links or places that I could go to read on these strategies?
I'm reluctant to put everything in one (or two) wixlib's since these are
dll's and exe's that contribute to the overall functionality of several
programs. Can't wix just 'ignore' when a wixlib has a reference to a file
t
Putting the same content in different .wixlibs is going to lead to no
end of troubles. I don't know the specifics but there are several ways
to restructure the example below to end up with content only in one
.wixlib. I highly recommend picking one of those strategies (for
example, you could pu
Ok, I'm sure this has been asked here before, but I wasn't able to find the
thread or a resolution...
How does anybody else deal with this situation:
I have several WiX projects that share common dependencies that I'm
compiling into wixlibs for larger projects. I want to ensure that a
compiled w
[EMAIL PROTECTED] wrote:
> Is there good documentation on how to detect application dependencies
Your dependencies should be explicit: Taking a dependency on a
particular component means keeping track of it, preparing for updates,
and so on.
> and locate suitable merge modules?
>
Always ge
I'm migrating our installer over from an InstallShield based solution to Wix.
With Installshield, all of our applications dependencies were automatically
detected, and the appropriate merge module was reccomended. My questions for
the list are...
Is there good documentation on how to detect a
Hi.
I use VS2005/MSBuild to build the MSI file. I experience that the
build step only depends on the wxs files and wixlib files. However the
resulting MSI file needs to be rebuilt whenever one of the refered
files have changed.
A line like
means that if filea.exe has changed then the MSI must b
17 matches
Mail list logo
