Page 1 of 1

Windows 7 - Program Files x86 instead of program files x64

Posted: Wed Dec 16, 2009 4:48 pm
by dunion
I've seen another post on this but no answer. I have program files set, it seems to install to the x86 directory when I require it to be x64. What is the best fix other than hard-coding this variable?

(That is, hard coding $PROGRAMFILES$ to "C:\\Program Files\\")

Posted: Thu Dec 17, 2009 5:51 am
by alibaba
Did you already set 64 bit operating system in design view >application requirements > special requirement ?

Posted: Thu Dec 17, 2009 7:43 am
by moorelife
Yes, I have it set, but on 64 bit machines, TARGETDIR keeps returning the X86 folder instead of the 64 bit one. And that means I'm restricted to installing on 32 bit machines. That is unacceptable, because some of our clients just cannot get what they want with the 32 bit application.

Thanks for any Assistance available.

Dre'

Did you ever get a reply to this?

Posted: Tue Dec 22, 2009 10:07 am
by dunion
I've been trying to hard-code this but am looking for the "real answer"?.

One Part of the Ans:The check-requirements scripts have bugs

Posted: Tue Dec 22, 2009 10:23 am
by dunion
Search on the forums works today! I found a past reference to looking at the 'check' scripts that get included with the project requirements. All of them reset the 'mode' back to 32 bit mode - especially the ones looking for 64-bit versions of runtime components. So I guess the 'real answer' would be to re-write these to 'read' the current state and restore the current state rather than just drop it into a fixed state; But I would think that by default someone looking for an x64 component probably is doing an x64 bit install and if we have to hard-code it, that probably makes the most sense.

At the bottom you can double click the Set x86 and select Set x64 in each of the scripts. This applies to the .net runtimes and VC runtimes, MSI runtimes, etc. Anything with a x64 at the end of the requirements.