|
Non-advertised shortcuts require dummy
HKCU keypaths in their components – do you have those? (This is one
of many mistakes ICE validation catches) Derek From: Dave Williamson
[mailto:[EMAIL PROTECTED] non-advertised shortcuts Have not delved into ICE validation yet
... see a little too much bantering back and forth about what is "passing
ICE validation". I'm too much of a newbie yet. Dave Williamson From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Derek Cicerone Are you using advertised or non-advertised
shortcuts? Did your MSI pass ICE validation? From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dave Williamson Based on an earlier email reply (8/1/2006
subject=Shortcuts) from Derek. In this reply Derek suggested that
shortcuts should not always be defined under the <File> but independently
because shortcuts and ALLUSERS don't always coexist in a manner that makes
sense. Some relevant facts on the *.wxs: Wix being used = v2 (wix_2.0.3719.0) Install sets ALLUSERS property to 1. Product ID and Package ID are changed with each release. and
<InstallExecuteSequence> So I took all my shortcuts out from within the <File>
elements and placed them within their own component elements. When this
new MSI is run on a workstation that has any previous install on it the old
shortcuts (desktop and startmenu) are left on the machine along side the new
shortcuts. Why were the old shortcuts not removed? Dave Williamson |
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
