Jul/100
Developing a provider for the Outlook Social Connector version 1.1
This post is syndicated from Microsoft Outlook 2010.
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
Oct/090
Outlook .pst file format and interoperability
This post is syndicated from Microsoft Office Outlook Team Blog.
This week, the Outlook product team hosted a .pst file format interoperability event here on the Microsoft campus in Redmond. As we announced on the Interoperability @ Microsoft blog, our team plans to release a specification of the .pst file format to the public. This week’s interoperability event is part of a series of steps that we are taking to gather feedback from industry partners and experts on preliminary drafts of the specification. If you are not familiar with the underpinnings of Outlook, .pst files are one type of data file that Outlook uses to save user data such as e-mail messages, contacts, and appointments.
During the interoperability event, we presented a preliminary specification of the .pst file format to selected industry experts in areas such as antimalware, electronic records management, data archiving, data recovery, and data migration. We collected useful feedback about our documentation roadmap, and the attendees were supportive of the direction and approach we are taking.
We understand our plan to document the .pst file format might cause some of our customers and partners to wonder about our commitment to MAPI (Messaging API) and the Outlook Object Model as interoperability mechanisms of Outlook. To us, the .pst file format specification doesn’t change the role of MAPI and the Outlook Object Model. While we are pleased to provide another mechanism to access data stored in .pst files, we continue to support MAPI and the Outlook Object Model as key elements of Outlook interoperability and extensibility. We do expect that the release of the .pst file format specification will open up new usage scenarios that were previously difficult to accomplish, especially in multi-platform and server scenarios where MAPI and the Outlook Object Model are not available.
Since we announced our plan to release the .pst file specification, we have received requests from people who want to participate in the review of early drafts of the specification. If you are interested in actively participating in the review of preliminary drafts of the .pst file format specification, send an email message to pstinfo@microsoft.com and then we will contact you when a preliminary draft of the specification is ready for broader review. If you only are seeking the final version, we anticipate releasing the .pst file format specification in the first half of 2010 under our Open Specification Promise.
Daniel Ko
Outlook Development Manager