This topic describes the supported programming languages, COM visibility and method return type requirements, and details of the Microsoft Outlook Social Connector (OSC) provider extensibility DLL.
Programming Language and COM Requirements
You can create an OSC provider by using managed languages such as Visual C# or Visual Basic, or unmanaged languages such as Visual C++. You can use any tool that can create a COM-visible DLL component to develop an OSC provider. The decision to use a managed or unmanaged language to develop a provider should take into account the download size and dependencies of the provider installation package.
An OSC provider must be COM-visible as defined by the following:
After installation, an OSC provider must be registered by using COM self-registration or regsvr32.
COM registration of an OSC provider DLL registers the provider under HKCU or HKLM.
A provider’s ProgID is registered under
An OSC provider developed in a managed language is COM-visible.
An OSC provider should add values to the Windows registry that indicate that the provider DLL supports both single-threaded apartment (STA) and multithreaded apartment (MTA) threading models. For more information about COM threading models, see Descriptions and Workings of OLE Threading Models.
Methods in OSC provider extensibility must return primitive types such as string or bool. Certain string return values must comply with the schema definition for OSC provider extensibility. Only XML is supported as a return value.
Details of the OSC Provider Extensibility DLL
The component that supports OSC provider extensibility is the OSC provider extensibility DLL. Third-party developers can build OSC provider DLLs by using these extensibility interfaces. The following list shows the details of the OSC provider extensibility DLL:
Extensibility DLL file name: socialprovider.dll
Extensibility DLL friendly name: Microsoft Outlook Social Provider Extensibility
Extensibility DLL major version: 14.0
Extensibiilty DLL TypeLib version: 1.1
Miscellaneous Technical Information
There are no dependencies on an XML parser. The OSC provider can use an XML parser that is included with Microsoft Office, such as Microsoft XML Core Services (MSXML), use the XML parsing capabilities built into the Microsoft .NET Framework, or use a third-party XML parser.