Thanks for the response but re-reading this I did leave out a crucial bit of info. I am aware of using the condition to create (or not) the shortcut depending on the state of the condition on the checkbox but this only aplies to the first install of the product. It is on Upgrade that I have the problem.
The scenario is this. I have installed for the first time and ticked the box and created the shortcut. I then upgrade the product and decide that I didn't want that shortcut after all. The box comes up ticked (we record the state of the box from the previous install in a HKLM registry key and then read that key to populate the checkbox) and so I untick it thinking this should remove the shortcut (as the client this is). From my testing this does not remove the already existing shortcut (not suprisingly). The HKLM registry entry changes from 1 (the checkbox checked value) to null (it is string not integer\DWORD and so will handle a null value) but the shortcut remains (as there is nothing to tell the install to delete it). What I am enquiring about is a mechanism to delete the existing shortcut on upgrade if the checkbox is unticked without resorting to a custom action calling an external executable (C++) if this is possible in WIX (3.0) land. Apologies for the confusion. SteveLoof wrote: > > I have 2 issues currently, one of which I think I am going to have to live > with and the other I am hoping someone has some suggestions for. > > I am relatively new to the world of WIX and am coming from using WISE for > Windows. In our Wise install we have a number of shortcuts for various > bits of our product and in varying locations (DesktopFolder, Quicklaunch > (which I haven't started wrestling with yet) and ProgramMenu). These are > turned on or off by the value given to the property associated with > checkboxes for each. As in Wise creating a shortcut is easy, it is > removing the shortcut if it is unwanted (the checkbox is unticked). In > Wise we used a custom action to run a del command from the command line in > a Wise Script. > > In WIX I amtrying to avoid having to write a C++ script to do the same > job. I have tried a <RemoveFile element with a condition on it > <Condition>SHTCUT01 <> 1</Condition>. The problem here seems to be > that the RemoveFile action is run before the shortcut file (textpad.lnk > for instance) is created and I can't sequence this step. Any other ideas? > > Also ICE38. I have read a bit about this and the reasons for it. We are > running no advertised shortcuts and don't expect self repair to > necessarily be available (we have a C++ script to look at the HKLM > registry settings (which we write as part of the install) and set up a new > users environment accordingly. I have to add not one but 2 useless > registry keys, one to create the shortcut and the other on the RemoveFile > component (even if that isn't the way to remove the shortcut I may need > that functionality elsewhere). Nobody seems to think this is a good test > for WI to be enforcing (for Vista certification need 0 ICE errors > (Microsoft Office has plenty of ICE errors)). Any idea if Microsoft are > planning to get rid of it? > > Thanks in advance. > > > -- View this message in context: http://www.nabble.com/Shortcut-removal-and-ICE38-silliness-tp16544966p16579196.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
