LabVIEW
Send file to program file not program file (x86) when building 32 bit installer
You don't. If you are compiling an application in 32-bit, you install to Program Files (x86). If you compile in 64-bit, then it goes into the Program Files. But you must use LabVIEW 64-bit to build 64-bit applications.
You can set the default install directory in the install options, or you can just manually input the desired path when installing.I misread the original post!
You don't have to worry about it. The 32-bit application will automatically get installed into the appropriate directory, depending on the "bit-ness" of the Windows operating system.
I agree with the others but I want to ask, why do you want to do this? Is there some requirement that you be installed in a certain location? Is something hard coded in older software? What is the reason for needing this, there might be other solutions.
@Hooovahh wrote:
I agree with the others but I want to ask, why do you want to do this? Is there some requirement that you be installed in a certain location? Is something hard coded in older software? What is the reason for needing this, there might be other solutions.
My assumption was that the OP had a 32-bit OS as a target and wondered how to make it go to "Program Files" instead of "Program Files (x86).
If your worries are about getting the program installed correctly into Program Files on a 32 bit Windows system, you don't need to worry. That automatically will work correctly.
If you want to install your 32 bit application into Program Files on a 64 bit system you can't do that. Windows actively forbids that. It doesn't like 32 bit executable files in the 64 bit reserved Program Files directory.
If you want to install another file than an executable there from your 32 bit installer, you most likely will have to add a batch file to your install that does the copy/move operation at the end of the installation to that location. The NI installer is not an installer environment that you can fully configure to all your possible strange desires, but provides a limited set of options in order to make its configuration in the Installer Builder manageable by an average to moderately advanced LabVIEW programmer.
