A verbose log file should tell you why the Component containing the shortcut decided not to be uninstalled.
Ali-Akber Saifee wrote: > > I have a shortcut that's created in the users My Pictures folder - > that points to a folder in my Application Directory. Upon > uninstallation, this shortcut to a folder, is not removed even though > the directory that it was pointing to was. We've tried adding the .lnk > file to the RemoveFiles table, but it still doesn't work. Any ideas? > > ./Ali > -------------------------------------------------------------------------- > > Subject: Re: [WiX-users] Shortcut to a folder > To: Cryptonomicon <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> > Cc: wix-users@lists.sourceforge.net > <mailto:wix-users@lists.sourceforge.net> > Message-ID: <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Cryptonomicon wrote: > > Is it possible to create a shortcut to a folder? > > > > Yes. See the Shortcut element doc in WiX.chm -- use [DirectoryId]. > > -- > sig://boB > http://joyofsetup.com/ > > > > > > ------------------------------ > > Message: 7 > Date: Tue, 06 Nov 2007 09:08:55 +0200 > From: "counterproductive" <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> > Subject: [WiX-users] Medical Doctor Directory > To: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>, [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>, > wix-users@lists.sourceforge.net > <mailto:wix-users@lists.sourceforge.net>, [EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>, > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>, > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>, > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>, > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > Message-ID: <[EMAIL PROTECTED] > Content-Type: text/plain; charset=US-ASCII > > > > > > > Fully Licensed Medical Doctors in the USA > > 788,733 in total – 17,917 emails > > Many different medical specialties > > Over a dozen sortable fields > > This week's special price = $492 > > > *** Get the data below as a gift when you order the MD list above *** > > US Pharmaceutical Executives Listing > 50000 personal emails and names for decision makers > > American Hospitals > 23,000 Admins in more than 7,000 hospitals {a $399 value] > > Dentists in the USA > A complete Listing or dentists and related services (valued at $299) > > US Chiropractor Database > 100,000 Chiropractors in the USA (worth $249 alone) > > call us: 206- 600-4472 > > > above offer valid until Nov 9 > > > > > > > ------------------------------ > > Message: 8 > Date: Tue, 6 Nov 2007 09:46:27 -0000 > From: "John Hall" <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> > Subject: Re: [WiX-users] Advertised feature install starting > To: "Bob Arnson" <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> > Cc: wix-users@lists.sourceforge.net > <mailto:wix-users@lists.sourceforge.net> > Message-ID: > <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> > Content-Type: text/plain; charset="us-ascii" > > I've got some machines that after a minor upgrade, > unprivileged users unexpectedly get MSI launching a dialog saying that > "the feature you are trying to use is on a network resource that is > unavailable". Administrators do not see the message. The installer was > run as Administrator. I assume it is because some features have been > installed as Advertised rather than Local. In my installer however, I > have marked all my features with AllowAdvertise="no", so > > > It's probably an automatic repair. Check the System event > log to > see which component MSI thinks is broken. > > > Bob, > > Thanks for the pointer. > > It's an HKCU registry key that would have been created for the > user who > installed the application, but obviously not the user who is > running. Is > this the default behaviour for a key in HKCU even if the feature > is not > advertised? > > In this case, it doesn't matter if the settings are not available for > the current user, and I would prefer MSI just to ignore these keys. > > Also, is this the expected behaviour? I thought that a copy of the MSI > was stored away in c:\Windows\Installer, so why is the system not able > to use that one rather than looking for the original .msi file > that the > bootstrapper dropped into the temp directory. > > Regards, > John > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a > browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > ------------------------------ > > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > <mailto:WiX-users@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/wix-users > > > End of WiX-users Digest, Vol 18, Issue 29 > ***************************************** > > > > > -- > Ali-Akber Saifee > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > ------------------------------------------------------------------------ > > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
