Unfortunately, making a 64-bit MSI isn't enough, since the user may have either 64-bit or 32-bit Outlook installed on their 64-bit OS. What's the best approach to this problem?
The simplest solution is to make a 64-bit MSI that checks for Outlook 2010 64-bit as a custom action or a launch condition as well as a 32-bit MSI that checks for everything else. The downside is this makes distributing the add-in through GPO quite difficult as the sysadmin must manually target the Outlook 2010 64-bit computers. Or, I could just make the MSI's without the check and let the sysadmin push both down and let the chips fall where they may, which would result in a 64-bit user getting both versions of the add-in installed, but only the one that matched the bitedness of their Outlook would run. Clunky, but effective.
Or, I could make a 64-bit MSI that contained both the 32-bit and 64-bit add-ins as features and automatically selected which feature to install. Is that feasible?
I'm trying to cover two cases here:
1. User downloads installer themselves. From experience, a user with a 64-bit OS will try to install the 64-bit add-in, even if they have Outlook 2010 32-bit (which they should), so need to automate the process as much as possible, or else block them from installing the wrong version. We can use the bootstrapper for this.
2. Sysadmin deploys add-in through GPO. This must be an MSI, and we can document the steps if the procedure is going to be complicated.
I can hack my way to some sort of solution, but any suggestions for anything resembling elegance would be greatly appreciated.
FOLLOW US
Get the latest news in Application Packaging