And it works in spite of the fact that Microsoft doesn’t guarantee it. If the add-in is to work in Office XP and higher, I use the official Office XP PIAs. I use Office 2000 PIAs generated by myself for add-ins that must work in all available versions of Microsoft Office. Scaring, isn’t it? But do you want to create special versions of your add-in for Office 2000, XP, 20? Or have you customers already upgraded their Office to 2007? I answered this question long ago. Therefore, if you build an add-in solution that you intend to use with both versions of Office, Microsoft recommends that you build a version of your add-in for each version of Office that you intend to support.
The Office 2003 managed code add-ins must be built against the Office 2003 PIAs. Office XP managed code add-ins must be built against the Office XP PIAs. Microsoft does not guarantee that the Office PIA will be backwardly compatible or that the Office XP PIA and the Office 2003 PIA can be run side-by-side in the same instance of an Office application. For Office 2000 there’re no official PIAs. There are official PIAs for Office XP and Office 2003 published by Microsoft. I will just say that they are very easy to use. For more details, please see the links below. And an Office PIA is an imported MS Office type library.
NET classes that wrap all interfaces of a COM type library. PIA is much more comfortable to use because it is a set of. Do you remember what type libraries ITypeInfo and ITypeInfo2 are? A PIA is, in fact, a COM type library imported to. There was OLE first, remember? Next there’s OLE Automation. What is the Office PIA and what should we do with it? To start with, a few words about PIAs, primary interop assemblies. Hey, somebody, stop me! :-) All in all, I’ve come to one of the key issues.
0 kommentar(er)
