In general, it is best to use the Outlook PIA rather than relying on an interop assembly from another source. As publisher of the type library, Outlook provides a Primary Interop Assembly (PIA) that contains the official description of the COM-based Outlook object model. Any number of interop assemblies can exist to describe a given COM type. NET.Īn interop assembly describes COM types and enables managed code to interact with a COM object model. NET and COM, see Introduction to interoperability between COM and. For more information about how interop assemblies facilitate interoperability between. Consequently, more Outlook solutions are now developed as managed applications that rely on an interop assembly. An interop assembly is a COM wrapper that acts as the bridge. NET and COM environments in order to program against a COM object model. However, a managed application needs a bridge between the. NET Framework provides a rich set of class libraries and support technologies that address many of the limitations of VBA and COM add-ins. However, Outlook solutions developed with VBA have deployment limitations, particularly in corporate environments, and are difficult to update after they are deployed. Historically, Outlook application developers developed COM solutions by using Visual Basic for Applications (VBA) and Visual Basic. This object model is designed to work with the Component Object Model (COM) technology. Starting in Outlook 98, Outlook provides an object model for developers to integrate Outlook functionality into an application, extend Outlook, or automate Outlook.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |