Where was the File installed? If it was to a per-machine location then
mixing in per-user stuff (like HKCU registry key) can create interesting
behaviors. Sorry, I don't remember more specifics but I know there is an ICE
that complains about it. Maybe that will lead to a trail...
On Thu, Dec 17, 2009 at 10:11 AM, XorPtr <reaper4...@gmail.com> wrote:
>
> Hey! I think I was able to finally solve this issue which also related so
> other issues with alternate patching not working. The reason for all the
> trouble seemed to be the use of RegistryKey entries for non advertised
> shortcuts in the related components. Original wix for example:
>
> <Component Id="Component1" Guid="{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}">
> <File Id="File1" Name="My File" Vital="yes"
> Source="$(var.PATH)\Filename.exe">
> <Shortcut Id="Shortcut1" Directory="ProductProgramMenuFolder" Name="File
> Name" WorkingDirectory="directoryBin">
> </File>
> <RegistryKey Root="HKCU" Key="Software\Product\NamedDirectory\Uninstall">
> <RegistryValue Value="0" Type="string" KeyPath="yes" />
> </RegistryKey>
> </Component>
>
> To fix the problem I had to remove the registrykey and set the shortcut as
> advertised as follows:
>
> <Component Id="Component1" Guid="{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}">
> <File Id="File1" Name="My File" Vital="yes"
> Source="$(var.PATH)\Filename.exe">
> <Shortcut Id="Shortcut1" Directory="ProductProgramMenuFolder" Name="File
> Name" WorkingDirectory="directoryBin" Advertise="yes">
> </File>
> </Component>
>
> In case anyone else out there has a similar issue, after making this change
> everything worked fine!
>
>
> XorPtr wrote:
> >
> > This is actually another cry for help on what's probably a related issue
> > with installing a patch when users install to an alternate directory.
> The
> > original issue was that when patching our product the patch only works
> > when the user installs to the default directory, if they choose their own
> > the patch does not work. The result of this was due to the patched files
> > installing into the default directory rather than the install directory.
> > Upon further investigation the same issue also occurs when repairing the
> > product if it is installed to a different directory. Removing the
> product
> > has a similar issue in not removing the files unless they're in the
> > default directory. At this point I'm confident the problem goes beyond
> > the patch and I'm making a basic mistake with the windows installer, but
> I
> > have no idea what I'm doing wrong.
> >
> > Thanks in advance!
> >
> > Big Jim.
> >
>
> --
> View this message in context:
> http://n2.nabble.com/Windows-installer-problems-when-users-choose-install-directory-tp4141782p4182655.html
> Sent from the wix-users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and
> easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
--
virtually, Rob Mensching - http://RobMensching.com LLC
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
