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.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/ ?
That unfortunately I cannot explain, you can look for a details answer on MSDN or StackOverflow.com.question 2; what is the difference then between compile as "32 bit" vs compile for "any cpu" in VS2012?
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.How does "any cpu"/32bit affect which package type you should choose from in Advanced Installer?
That is correct. This is the option that I recommend for you.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.
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?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?
Bogdan wrote:Hi,
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.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/ ?
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).
That unfortunately I cannot explain, you can look for a details answer on MSDN or StackOverflow.com.question 2; what is the difference then between compile as "32 bit" vs compile for "any cpu" in VS2012?
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.How does "any cpu"/32bit affect which package type you should choose from in Advanced Installer?
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.
That is correct. This is the option that I recommend for you.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.
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.
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?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?
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
FOLLOW US
Get the latest news in Application Packaging