|
1,2. I don’t understand your pseudo-code.
ComponentRef’s can’t have File elements under them. I’m
not sure how to interpret Situation 1 and 2. It would also be helpful to
know what the symbol the error is complaining about. 3. The “-ai” switch *may* be broken in
WiX v3. There have been some big changes in v3 to support nesting of
ComponentGroups and I never tested “-ai” after it (totally slipped
my mind). However, again, the exact error message and exact layout of all
of your files is important to understand what is going wrong. From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wilson,
Brad wix
version 3.0.1828.0 When
calling light against install projects there are a few situations that are
causing problems for us when designing our installs. All of these
situations cause the "Duplicate Symbol found' error. Situation
1 (this is pseudo-code): Feature1 - ComponentRef1 - File1 - ComponentRef2 - File2 Feature2 - ComponentRef2 - File2 - ComponentRef3 - File3 <Product ...> <FeatureRef id="Feature1" ... > <FeatureRef id="Feature2" ... > </Product> This
is causing a Duplicate symbol error on File2. It was my assumption that
components could belong to multiple Features if using
<ComponentRef>. Situation
2: If
I were to create a ComponentGroup and include File2 in it and then use
<ComponentGroupRef> in Feature1 and Feature2, I would also get the
'Duplicate Symbol' error but this time it would be on the ComponentGroup. Situation
3: I'm
not sure that this last situation is a bug. But it's something that I
would hope would work or it might undermine our usage of nested component
groups. In our situation there are a lot of files that belong to many
different applications. Our hope was to be able to nest ComponentGroups
to be able make a modification to one ComponentGroup and have it affect lots of
different installs. Here is the situation: ComponentGroup1 - ComponentGroupNest1 - ComponentGroupNest2 ComponentGroup2 - ComponentGroupNest2 - ComponentGroupNest3 <Feature ...> <ComponentGroupRef
id="ComponentGroup1" /> <ComponentGroupRef
id="ComponentGroup2" /> </Feature> We
were hoping that light would be smart enough to understand that, since those
files are included from multiple ComponentGroups, to just ignore any multiples
of that file for that feature. Instead, we get the Duplicate symbol error
on ComponentGroupNest2. I've
tried all of this with the -ai command line option for light.exe but i'm
getting a SystemNullReference exception. To get this to work, is -ai
supposed to be used or should the three situations work w/o a specific command
line option? Brad
Wilson | Developer |
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
