Sorry Grant,  no guided tours when your skiing the backcountry.  You gotta be 
able to hold your own on this one. :-)   My only clues are to make sure you 
understand the difference between SetProperty (51) and SetDirectory (35) custom 
actions.  How costing works and servicing implications for install, uninstall, 
maintenance and patch / upgrade.   If you think it through you should be fine 
as 
long as the MSI team never "fixes" this which I'm guessing they never will.

Chris
 
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves 
attention? E-Mail Me



----- Original Message ----
From: garnold <grant.arn...@safe.com>
To: wix-users@lists.sourceforge.net
Sent: Mon, September 20, 2010 6:20:00 PM
Subject: Re: [WiX-users] How to allow 32-bit installer to writetoC:\ProgramFiles


Thanks for the replies.  This sounds like a giant pain.  It's horrible that I
can't tell the installer the exact directory that I want some files in.  It
just changes it without telling me it's going to, and there is nothing I can
do to stop it.  Couldn't they have at least made some kind of override
option?  Sigh.  It's so weird because I want to specify a directory that
already exists, and it changes it to a directory tree that doesn't exist and
creates it for me...

Anyways, making a separate installer for x64 components doesn't seem like a
workaround to me, because it doesn't solve the problem.  It just splits my
installer into two installers, which is horrible.  I will attempt Chris
Painter's suggested workaround.  

Chris:  When should I schedule the custom action?  Before='InstallFiles' in
the InstallExecuteSequence?  Does it just read in the value of the property
for that directory, and then replace 'Program Files (x86)' with 'Progra~1'? 
The other issue I see is that in the dialog when you browse to the
directory, the SetTargetPath will also change the Program Files to Program
Files (x86) which will be confusing for a user...

Thanks,
Grant
-- 
View this message in context: 
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-allow-32-bit-installer-to-write-to-C-Program-Files-tp5544693p5552677.html

Sent from the wix-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users



      

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to