In vsto, office development always encounters the Office version problem. Different versions may encounter compatibility problems. In the past, we used C ++ to develop word 2000/2003.ProgramTo make a program available in 2000/2003, TLB is imported into the database based on version 2000. Due to the forward compatibility of the Office, the problem can also be solved. Of course, new features cannot be used.
In the hosted environment, Pia is introduced, and the hosting program communicates with the COM component of office. Currently, there are four versions of Pia in Office 2000/20003/2007/2010. If you use a method compatible with a lower version, for example, if the lowest version supports 2003, you only need to deploy 2003 Pia, but the functions introduced by a new version cannot be used.
Http://blogs.msdn.com/ B /andreww/archive/2008/09/02/version-specific-ui-in-add-ins.aspx handling methods each version uses its own Pia while maintainingCodeThe method is worth referencing in the project, otherwise it would be a nightmare to maintain so many versions. Of course, when using this method, you need to determine the correct installation of the corresponding version of Pia during deployment.
Here is a detailed reference directory:
Http://blogs.msdn.com/ B /andreww/archive/2008/06/03/add-ins-for-multiple-office-versions-without-pias.aspx
Add-ins for multiple Office versions without PIAs
Http://blogs.msdn.com/ B /andreww/archive/2007/06/08/why-is-vs-development-not-supported-with-multiple-versions-of-office.aspx
Why is vs development not supported with multiple versions of office?
Http://blogs.msdn.com/ B /andreww/archive/2007/06/15/can-you-build-one-add-in-for-multiple-versions-of-office.aspx
Can you build one add-in for multiple versions of office?
Http://blogs.msdn.com/ B /andreww/archive/2008/06/24/add-ins-for-multiple-office-versions-without-pias-pt2-or-vtblgap.aspx
Add-ins for multiple Office versions without PIAs (pt2), or _ vtblgap
Http://blogs.msdn.com/ B /andreww/archive/2008/09/02/version-specific-ui-in-add-ins.aspx
Version-specific UI in add-ins