We have some components that are the same file names but different DLLs.
For the sake of the example, let's say they're x86 vs. x64 versions of a
file. Here is what the feature looks like:
<Feature Id="ServicesFeature">
<Feature Id="PrintServiceFeature">
<ComponentGroupRef Id="PrintComponents" />
</Feature>
</Feature>
<ComponentGroup Id="PrintComponents">
<ComponentGroupRef Id="ArchitectureBasedPrintComponents" />
</ComponentGroup>
<ComponentGroup Id="ArchitectureBasedPrintComponents">
<Component Id="SomeFile_x86">
<Condition><![CDATA[IS_X86 = "1"]]</Condition>
<File Id="SomeFile_x86_dll" Source="x86\SomeFile.dll" />
</Component>
<Component Id="SomeFile_x64">
<Condition><![CDATA[IS_X86 <> "1"]]</Condition>
<File Id="SomeFile_x64_dll" Source="x64\SomeFile.dll" />
</Component>
</ComponentGroup>
The <Condition /> elements for either the x86/x64 properly honors the
IS_X86property. However, through ARP when you "Change" the application
by going
through the UI sequence and choosing the other architecture (for the sake
of this example), it does not install the correct DLL.
So, if you had initially installed the x86 copy, when you go through the
"Change" and tell it x64, the x64 DLL does not get installed.
I'm sure it's something obvious, but I'm not verse enough with how Windows
Installer handles this situation.
Thanks in advance,
Levi
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
