such a simple solution and it worked, thanks for pointing that out! as far as
using multiple files, my intention is to go away from that. i am making heavy
use of the preprocessor so i can reuse components making them slightly
different based on the variables set. thanks again. should i write th
I am currently using the stable 2.0 binaries to build my installer. Currently
today i have multiple wxs files, 2 for individual msm's and 1 to include those
msm's to build a few msi's. now, what i would like to do is consolidate down to
a single wxs and still retain the ability to net the same o
thanks, what about module/id?
Bob Arnson wrote:
> Jeremy Breiding wrote:
>> I would like to use the packagecode generation built into the
>> compiler.
>
> Package codes aren't generated until bind time, so they're not
I would like to use the packagecode generation built into the compiler.
However because of some of my customizations I have to hard code the
packagecode because this is needed to identify some components of the
msm. Is there a way to access the generated one via $(var.packagecode),
which actua
4 matches
Mail list logo
