Seems I am somewhat misinformed.
Marco Amoedo has added the following comment:
There is support for VSTO Add-ins on 64 and 32 bits already for Office 2010 and it is available with the betas of VS 2010 and Office 2010. Moreover, for the managed .Net add-ins created with previous version and compiled to target any-cpu there won’t be any problem. Well, providing that you don’t use any p-invoke. There is more info at MSDN.
In the case of the CRM Add-in. It is not actually a VSTO Add-in as it is not managed .Net code. Therefore it needs to be specifically compiled for the 64 bits platform. I would expect an updated by the Office 2010 RTM to solve the 64 bits issue.
Many thanks for clarifying this.
I am noticing a bit of a 32-V-64 bit clashes coming down the line.
I have migrated most of my machines to Windows 7, 64 bit but Office 2007 is only 32 bit which is not a problem. I am also in the market for a new machine for a family member and I notice that a large number, possibly the majority, are shipping with the 64 bit version of the operating system.
Now office 2010 finally ships with a 64 bit version. However, I see that PCPro warns that some aspects of Office 2010 wont work with 64 bit versions and I also read that the CRM 4 client wont work either. The primary culprit is the fact that most add-ins are based on COM and activeX and there is not currently a 64 bit Visual Studio Tools for Office runtime. Lets hope this does come together well in advance of RTM.