Export (0) Print
Expand All

Quick Steps for Learning to Develop a Provider

This topic suggests a few steps to learn about developing a Microsoft Outlook Social Connector (OSC) provider.

Summary of Steps to Develop an OSC Provider

To develop an OSC provider, you need to complete the following general steps:

  • Implement the four mandatory interfaces: ISocialProvider, ISocialSession, ISocialProfile, and ISocialPerson. Depending on your social network’s support for caching logon credentials, following a person on the social network, or dynamically synchronizing friends and their activities, you might want to implement the ISocialSession2 interface.

  • In parallel with implementing interfaces, test and debug the OSC provider.

  • Deploy the OSC provider.

  • Do final testing before release.

Step A: Implementing Interfaces

An OSC provider implements interfaces so that the OSC can use these interfaces to obtain necessary information about or from the social network, through the OSC provider. Such information includes the following:

  • How to present the account logon dialog to a user.

  • Whether the provider supports showing friends or activities as displayed on the social network.

  • How to display friends and activities in the People Pane.

  • When to refresh friends or activities information on the People Pane.

The information is typically passed from the provider to the OSC, in the form of XML strings as output parameters of interface methods. Both the OSC and an OSC provider comply with the OSC provider XML schema. Therefore, in the course of implementing the interfaces, you need a good understanding of how the XML schema allows you to specify information as listed above. The following resources explain how to specify XML for provider capabilities, friends, and activities:

Before you start implementation, also consult the following topics to save you time later in the debugging process:

Step B: Debugging

The topic Debugging a Provider suggests debugging procedures you can use while developing an OSC provider.

While you are developing, you can also refer to Getting Ready to Release an OSC Provider to gain a better understanding of the expected behavior in certain scenarios (for example, basic and forms-based authentication).

Step C: Deploying

See the following topics to learn about deployment requirements:

Step D: Final Testing Before Release

Depending on your social network and the OSC provider, there are usually provider-specific tests you should carry out before you release your provider. For a suggested list of tests, see Getting Ready to Release an OSC Provider.

See also

Community Additions

ADD
Show:
© 2014 Microsoft