We use Wix 3.0.4805.0.
We run into a very strange link error: we have a component that uses "*" as the
GUID. But when we link it, it reports an error:
error LGHT0204 : ICE08: Component: RegistrySpecial has a duplicate GUID:
{A7C1768B-FF73-5DFC-8E76-E810E013F78A}
But I searched all of our source code, there is no GUID
"{A7C1768B-FF73-5DFC-8E76-E810E013F78A}" defined anywhere.
Here is the command line to compile and link it:
candle.exe -dRelease -out <.wixobj file> -arch x86 -ext <ext dll files>
myapp.wxs
light.exe -ext <EXT_DLL_FILE> -cultures:en-us -out myapp.msi -pdbout <PDB_FILE>
-loc <LANG_FILE> <some .wixobj files>
Basically, this is what we'd like to do:
there is an option called "Start application when Windows starts". If the end
user select this option, we'll write the application's file path to a registry
entry; if the end user doesn't select this option, we'll also write the entry
with a parameter. The logic is just like this:
if (RUNWHENWINDOWSSTART) {
write registry with "[PATH_TO_APP]"
} else {
write registry with "[PATH_TO_APP] -bootload"
}
Here is the code:
<Component Id="RegistryNormal" Guid="*">
<Condition>RUNWHENWINDOWSSTART = 1</Condition>
<RegistryKey
Root="HKCU"
Key="Software\Microsoft\Windows\CurrentVersion\Run"
Action="create">
<RegistryValue
Type="string"
Name="$(var.ProductName)"
Value='"[INSTALLLOCATION]$(var.FileOutput)"'
KeyPath="yes"
/>
</RegistryKey>
</Component>
<Component Id="RegistrySpecial" Guid="*">
<Condition><![CDATA[RUNWHENWINDOWSSTART <> 1]]></Condition>
<RegistryKey
Root="HKCU"
Key="Software\Microsoft\Windows\CurrentVersion\Run"
Action="create">
<RegistryValue
Type="string"
Name="$(var.ProductName)"
Value='"[INSTALLLOCATION]$(var.FileOutput)" -bootload'
KeyPath="yes"
/>
</RegistryKey>
</Component>
I thought "*" will generate GUID for each component. But how come it reports
that error? And it's always that ID. What is special about that ID? The
interesting thing is, if I delete one of the two components from the code, the
compile/link is fine. So it seems the root of the problem is that I'm having
these two components at the same time. Why I can't have these two components at
the same time? This is really a if-then-else scenario. Maybe I shouldn't have
two components to implement the logic? Is there any other way to implement this?
Thanks.
/Brian
__________________________________________________________________
Looking for the perfect gift? Give the gift of Flickr!
http://www.flickr.com/gift/
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
