Developing a provider for the Outlook Social Connector version 1.1

Following the release of the Outlook Social Connector (OSC) version 1.1 and the availability of new and updated providers, we have released a set of updated and expanded content for developers. The Outlook Social Connector 1.1 Provider Reference incorporates content from OSC 1.0 with new additions for OSC 1.1.

If you’re developing a provider for the OSC, here is a quick guide to the new provider reference on MSDN:

  • Getting Started with Developing an Outlook Social Connector Provider helps you understand why and how to develop a provider. For developers who are just getting acquainted with OSC provider development, I especially recommend the topic entitled Quick Steps for Learning to Develop a Provider.
  • Updated content on provider deployment and packaging. See the topic entitled Installation Checklist for guidelines about building a provider installation package. Although OSC 1.1 is not redistributable, you can link to the appropriate OSC 1.1 installer using a GLINK.
  • Completely new content on testing a provider. See the section entitled Getting Ready to Release an OSC Provider. This section contains the complete guide for your Quality Assurance team to fully test provider installation, authentication, and core OSC features such as contact and activity sync.
  • Updated code samples for OSC 1.1. The code samples include a working sample provider and provider templates for Visual Basic, Visual C#, and C++. The code samples require Microsoft Visual Studio 2008 or Microsoft Visual Studio 2010.

If you are a developer interested in building a provider for the Outlook Social Connector, review this new reference content on MSDN. If you have questions or issues with the documentation, contact us at oscprex@microsoft.com. Happy coding!

Randy Byrne

Microsoft Outlook Program Manager

Office Blogs Comments

Comments: (2) Collapse

  • Can you authenticate with a service using OAuth2 for outlook social connector? I can see that username/pwd authentication works great but I cannot find an easy way or sample to use OAuth2. Any help is appreciated.

  • Request: Is it possible to implement on-demand synchronization for a provider without using hashed email addresses. Issue is that the social network I am trying to work with does not support hashed email addresses, which makes implementing on-demand synchronization using hashed email addresses much more hard, complex and inefficient.

Comments

Comments: (loading) Collapse