On 12/13/2013 11:21 PM, Bevan Weiss wrote:
> I would suggest using two separate components for it.
> Each Shortcut is really a file..
> Then each would get its own HKCU registry entry.
>
> Is your installer PerUser or PerMachine?
> The HKCU entry might not be so appropriate for a PerMachine install.
As I stated below my snippet, I already tried it with a separate
component (complete with another dummy registry entry), but Windows
Installer still does not create the second shortcut.
Maybe the problem is that both Shortcuts actually piggyback on
"myapplication.exe" in some way - I'm getting one warning when I create
my installer:
warning LGHT1076 : ICE69: Mismatched component reference. Entry
'ApplicationStartMenuShortcut' of the Shortcut table belongs to
component 'ApplicationShortcut'. However, the formatted string in
column 'Target' references file 'myapplication.exe' which belongs to
component 'myapplication.exe'. Components are in the same feature.
Thanks for pointing out the HKCU thing. The registry entry isn't used
for anything but maybe putting it in HKLM is better since the install is
per machine.
Regards,
Markus Ewald
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
