My specific scenario is creating an Office add-in (VSTO using .Net AnyCPU), but I expect there are others. At the moment I have the following options:
1. Create 2 separate projects, one 32 bit, one 64 bit.
2. Create an install that works on both 32 bit and 64 bit and then mess around trying to put the registry entries in the right place. This also involves trying to work out whether the installed Office version is 32 bit or 64 and there doesn't seem to be a reliable method for this.
So it would be nice to create 32 bit and 64 bit versions using the SAME project. Alternatively if you can come up with a reliable way of detecting office bitness and ideally build it into the product, plus a less tortuous way of deciding whether registry entries (and programs?) go in the 32 bit or 64 bit locations that would be good
