We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

b.biene
Posts: 66
Joined: Thu Nov 08, 2012 4:21 pm

32bit Installer on 64bit

Is it possible to create a 32bit installer and install the software on 64bit systems in the "program files" folder? (not the "Progam Files(x86)")
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: 32bit Installer on 64bit

Hi,

No, it is not possible. Windows is automatically redirecting the installation into "Program Files(x86)" folder.

All the best,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
tslewis
Posts: 65
Joined: Wed Mar 13, 2013 7:06 am

Re: 32bit Installer on 64bit

Thats not my experience when using a mixed 32/64 bit installer. 32 bit assmeblies are placed in a 32bit folder and program files on a 64 bit OS. Why is this? Using advanced installer 10
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: 32bit Installer on 64bit

Hi,

Please keep in mind that this is the normal behavior. A mixed 32/64 bit installer contains both 32-bit and 64-bit packages. So, when you install your application, the corresponding package will be launched depending on your Operating System bitness and that's why the application is installed in the "Program Files" folder (the 32-bit package is launched on a 32-bit Operating System and the 64-bit package is launched on a 64-bit Operating System).

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
tslewis
Posts: 65
Joined: Wed Mar 13, 2013 7:06 am

Re: 32bit Installer on 64bit

I just read this link

http://www.advancedinstaller.com/user-g ... types.html

So for a mixed 32/64 bit package, deployed on a 64 bit OS, why is my 32 bit assembly still deployed to ProgramFiles/Manufacturer/Productname/32bit/ by defulat and not ProgramFilesx86/Manufacturer/Productname/ ?

What I don't understand I guess is the significance of package types, in particular how they relate to the compiled assembly one wishes to deploy. Does the term "package" relate to the type of assembly or to the type of OS to which an assembly is to be deployed to?

Right now I am trying to interact with an application - say Excel - that may be either 32 bit or 64 bit. My assembly is 32 bit to account for both possibilities. I am not compiling a separate 64 bit and 32 bit assembly. The option I am using in VS2012 is compile to "any cpu". Question here is, I assume this implies my assembly is compiled as 32 bit as it can run on 32 bit and 64 bit - any cpu. Hence, question 2; what is the difference then between compile as "32 bit" vs compile for "any cpu" in VS2012? How does "any cpu"/32bit affect which package type you should choose from in Advanced Installer?

As I understand it from the link above, there are 3 package types:

Option 1: 32 bit package
Option 2: 64 bit package
Option 3: mixed 32/64 bit package

Now, I presume that in Option 1 I can deploy a 32 bit assembly (any cpu assembly/32 bit assembly?) to both a 32 bit os and 64 bit os. The caveat being that for 64 bit os the assembly is deployed to programfilesx86 not programfiles.

Option 2; obviously only works for a 64 bit os and the assembly is deployed to Programfiles

I am confused about option 3. I would have expected that this allows for me to have one EXE to selectively deploy my 32 bit assembly to the correct folder independent of the OS i.e. ProgramFiles for 32 bit OS and programfilesx86 for 64 bit os. However, the confusion I have is, this does not happen for me when I use a mixed package. My 32 bit assembly is deployed to programfiles on the 64 bit os not the programfilesx86 folder. And this is the default action using the mixed 32/64 bit wizard. I didn't specify this. I understand that there is a parameter called AI_Programfiles for this type of package but it does not correctly deploy my assembly correctly. Do I need to resolve paths or something? What am I missing here? What went wrong?

It seems crazy that I would have to create two installer packages for a 32 bit assembly to deployed on 32/64 bit os and then another installer for a 64 bit assembly to install on a 64 bit OS. Surely this is the point of a mixed 32/64 bit installer, being able t deploy both a 32bit and a 64 bit assembly to any OS? What am I missing?

cheers
tslewis
Posts: 65
Joined: Wed Mar 13, 2013 7:06 am

Re: 32bit Installer on 64bit

Also the mixed package wizard does have an option to install 32 bit files onto a 64 bit os, so i am really confused
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: 32bit Installer on 64bit

Hi,
So for a mixed 32/64 bit package, deployed on a 64 bit OS, why is my 32 bit assembly still deployed to ProgramFiles/Manufacturer/Productname/32bit/ by defulat and not ProgramFilesx86/Manufacturer/Productname/ ?
Let me give you some more insight on how mixed packages work. These are not supported by Windows by default, the way we make it work is that we build two MSIs (x86 and x64) and a a shared CAB file containing the resources to be installed.
Our EXE will extract them and launch the appropriate MSI, base on the machine architecture. On the x64 bit machine it will launch the x64 MSI, which will always write to Program Files folder, never to Program Files (x86) folder.
This is why on a x64 machine your 32 bit files go in the folder you mention.

Only 32 bit MSI package can write to Program Files (x86).
question 2; what is the difference then between compile as "32 bit" vs compile for "any cpu" in VS2012?
That unfortunately I cannot explain, you can look for a details answer on MSDN or StackOverflow.com.
How does "any cpu"/32bit affect which package type you should choose from in Advanced Installer?
It does NOT affect it. As long as you don't have files that need to go to Program Files folder on a x64 machine you should go with a simple x86 package type, not a mixed one.
The x86 package will install correctly on all machines, on x64 machines it will write the files to Program Files (x86) folder.
Now, I presume that in Option 1 I can deploy a 32 bit assembly (any cpu assembly/32 bit assembly?) to both a 32 bit os and 64 bit os. The caveat being that for 64 bit os the assembly is deployed to programfilesx86 not programfiles.
That is correct. This is the option that I recommend for you.

I understand that there is a parameter called AI_Programfiles for this type of package but it does not correctly deploy my assembly correctly
This property does resolve correctly, as it should. As I explained in the beginning of my post, with a mixed package you can never write into Program Files (x86) folder on x64 machine because the x64 MSI is launched,
which cannot access this folder.
It seems crazy that I would have to create two installer packages for a 32 bit assembly to deployed on 32/64 bit os and then another installer for a 64 bit assembly to install on a 64 bit OS. Surely this is the point of a mixed 32/64 bit installer, being able t deploy both a 32bit and a 64 bit assembly to any OS? What am I missing?
From what I understood you have only one DLL, configured to "Any CPU", so I don't understand where is the problem if you will use only a 32 bit application. Can you please give me more details on this?

Best regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
tslewis
Posts: 65
Joined: Wed Mar 13, 2013 7:06 am

Re: 32bit Installer on 64bit

Thank you very much for the great support. I apologize if my questions are overly obvious or stupid. I am finding the installer process of deploying code pretty complicated!

I believe you have explined the mixed package in some clarity now.

What confused me was I was under the impression that 32 bit files on a 64 bit OS had to be placed in the Programfiles(x86) folder which was not what I expereinced when using the mixed package. I thought I had made a mistake in the installer settings and that was the source of errors downsteram. I understand a x86/32bit package resolves this. Thanks for clarifying the difference.
Bogdan wrote:Hi,
So for a mixed 32/64 bit package, deployed on a 64 bit OS, why is my 32 bit assembly still deployed to ProgramFiles/Manufacturer/Productname/32bit/ by defulat and not ProgramFilesx86/Manufacturer/Productname/ ?
Let me give you some more insight on how mixed packages work. These are not supported by Windows by default, the way we make it work is that we build two MSIs (x86 and x64) and a a shared CAB file containing the resources to be installed.
Our EXE will extract them and launch the appropriate MSI, base on the machine architecture. On the x64 bit machine it will launch the x64 MSI, which will always write to Program Files folder, never to Program Files (x86) folder.
This is why on a x64 machine your 32 bit files go in the folder you mention.

Only 32 bit MSI package can write to Program Files (x86).
question 2; what is the difference then between compile as "32 bit" vs compile for "any cpu" in VS2012?
That unfortunately I cannot explain, you can look for a details answer on MSDN or StackOverflow.com.
How does "any cpu"/32bit affect which package type you should choose from in Advanced Installer?
It does NOT affect it. As long as you don't have files that need to go to Program Files folder on a x64 machine you should go with a simple x86 package type, not a mixed one.
The x86 package will install correctly on all machines, on x64 machines it will write the files to Program Files (x86) folder.

I udnerstand I dont need files to go in PorgramFiles and I WNAT them to go in ProgramFilesx86 but now intead of having one Advanced installer project (mixed package) to handle both 32 bit and 64 bit programs and files I have to have two separate ones.
Now, I presume that in Option 1 I can deploy a 32 bit assembly (any cpu assembly/32 bit assembly?) to both a 32 bit os and 64 bit os. The caveat being that for 64 bit os the assembly is deployed to programfilesx86 not programfiles.
That is correct. This is the option that I recommend for you.

I understand that there is a parameter called AI_Programfiles for this type of package but it does not correctly deploy my assembly correctly
This property does resolve correctly, as it should. As I explained in the beginning of my post, with a mixed package you can never write into Program Files (x86) folder on x64 machine because the x64 MSI is launched,
which cannot access this folder.

OK got it now, I understand that a 32 bit file is deployed in a diferent folder on a 64 bit OS for a mixed package than for a 32 bit package.
It seems crazy that I would have to create two installer packages for a 32 bit assembly to deployed on 32/64 bit os and then another installer for a 64 bit assembly to install on a 64 bit OS. Surely this is the point of a mixed 32/64 bit installer, being able t deploy both a 32bit and a 64 bit assembly to any OS? What am I missing?
From what I understood you have only one DLL, configured to "Any CPU", so I don't understand where is the problem if you will use only a 32 bit application. Can you please give me more details on this?

Because based on prior information I received it was suggestive that for a mixed package you can only install 32 bit files on a 32 bit OS and 64 bit files on a 64 bit OS. I understand now that isnt true and 32 bit files in a mixed package can be insatlled on a 64 bit OS BUT in different folder to what a 32 bit file would be deployed if I used a 32 bit package............

I know the DLL is currnetly only 32 bit but I do in the near future want to offer a 64 bit version. I wanted to have one AI project to do this instead of two. And I wanted 32 bit progrman files installed in the x86 folder on a 64 bit OS.

Is it possible to resolve the path to an x86 folder on a 64 bit OS?

Again , thanks for support


cheers


Best regards,
Bogdan
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: 32bit Installer on 64bit

My pleasure.

Best regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”