Some observations:
1) My package has InstallScope="perMachine" because if I left it at
the default, my shortcuts showed up in my user's profile (not "all
users").
2)
I need to create a shortcut for the user's manual:
<Component Id="swemm3man"
Guid="4e4f1188-a166-44ab-a7c6-3ed72207fef3">
<RegistryValue Root="HKCU" Key="$(var.MM3RegKey)"
Type="string" Value="" KeyPath="yes"/>
<File Id="swemm3man"
Source="$(var.Binaries)SWE\MM3Manual.pdf">
<Shortcut Id="swemanshort"
Name="Användarhandledning" Directory="SweDoc" Advertise="no"
Description="Visa användarhandledningen till Mikromarc 3-klienten"/>
</File>
</Component>
Without <RegistryValue> I get error "ICE43: Component swemm3man has
non-advertised shortcuts. It should use a registry key under HKCU as
its KeyPath, not a file.".
But with <RegistryValue> left in, I "only" get the warning "ICE57:
Component 'normm3hlp' has both per-user and per-machine data with an
HKCU Registry KeyPath."
Changing the RegistryValue's Root to "HKMU" turns ICE57 into an error
(rather than a warning).
3) I could of course turn it into an advertised shortcut, but then the
icon goes AWOL.
4) Well, I could do 3) AND supply an icon of my own, which would look
strange to the user because chances are he is using a different
pdf-reader than mine.
I've googled my little heart out, and can't find a way other than to
ignore the ICE57 warning (along with some potential registry pollution
that most users consider to be inevitable these days anyway).
--
Rune
------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
