This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Hard-code "c:\Program Files"
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 16, 2010
09:11 AM
Hard-code "c:\Program Files"
I have an application that has batch files that point to "c:\Program Files" - When I install the .MSI in Windows 7 64bit, it is using the ProgramFiles variable(c:\Program Files (x86), path and not the hard coded path I put in. Even though I put in C:, and the Program Files underneath that as the documentation suggests.
I have the seen the forums on creating a hybrid project and doing some scripts, but that is all a little over my head right now and I was just trying to do this through the Project Assistant.
I have the seen the forums on creating a hybrid project and doing some scripts, but that is all a little over my head right now and I was just trying to do this through the Project Assistant.
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 16, 2010
12:57 PM
Officially, MSI will substitute even hard coded references to program files as part of an application compatibility approach ( basically microsoft assumes you didn't know what you were doing and that they know what you really meant to do ).
Unofficially- read this thread to find a hack that I figured out to work around this.
http://www.joyofsetup.com/2010/03/27/wix-msbuild-v2-0-and-x64-systems/
Unofficially- read this thread to find a hack that I figured out to work around this.
http://www.joyofsetup.com/2010/03/27/wix-msbuild-v2-0-and-x64-systems/
Not applicable
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 19, 2010
10:23 AM
Thank you - After reading through comments on that blog I found someone say to use "C:\Progra~1" - It worked for me.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 19, 2010
11:18 AM
That was me. 🙂
Realize though that Microsoft might 'fix' this in a future release of the windows installer.
Realize though that Microsoft might 'fix' this in a future release of the windows installer.