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
6 matches
Mail list logo
