Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Conditional DLL install Based on Outlook Bitness value

Hello Rohit,

Indeed, you cannot select the Mixed 32/64-bit matching the platform option as a package type and use the Per-machine if user is administrator, per-user otherwise option for the installation type.
Also, let's consider the following scenario:
Your package type is a Mixed 32/64 - bit. That means the installer runs as a 32-bit on 32-bit platforms and as 64-bit installer on 64-bit platforms.

What will happen if your target machine is on 64-bit and the Outlook Bitness value is 86. In this case you need to add your .DLL in the Program Files (x86) isn't it? Unfortunately, you cannot write to that location since your package runs as a 64-bit installer on 64-bit platforms.

I think you may overcome this if you create your installation package as a 32-bit package package type which will be used when the bitness value for Outlook is 86 (since you need to add your .dll in the Program Files for the 32-bit machines and Program Files (x86) for the 64-bit machines) and create create another installation package which will be added as a prerequisite to main installation package and which will only run when the bitness value of Outlook is 64 (of course you are running on a 64-bit machine).

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
guypb
Posts: 28
Joined: Thu Dec 18, 2008 5:16 pm

Re: Conditional DLL install Based on Outlook Bitness value

Sorry to resurrect this.
Has anyone worked out where the bitness key is for x64 office 365?
This may be a red herring, but my standard methods for Office 2010 & 2013 did not work for the Office 2016 preview version.
Is this because the preview is using some "non production" registry keys, or because it is an Office 365 deploy?

Anyone else found this - maybe with previous versions?

Return to “Common Problems”