Integrating and Extending Office Communicator

David OllasonPrincipal Lead Program ManagerMicrosoft Corporation

PR13

Agenda> Introduction

> Availability and supported technologies> Feature Overview

> The Client Platform> Integrating Office Communicator

capabilities into your apps> Making conversations contextual> Extending Office Communicator> The OC 14 Managed API

> Summary

UC 14 Metro Program An opportunity for early adopters> Your Commitment:

> Must have NDA> Must have project scoped/planned

> Your Benefits:> Early access to UC 14 products and SDKs> Technical briefings> Training> Support

> Getting Nominated:> Talk to your Microsoft representative> Don’t know who to ask? Email

metroreq@microsoft.com

IntroductionSupported Technologies> Visual Studio 2010> Silverlight 4.0> .Net 3.5+> IE 7.0 and 8.0

Search, BrowsePresence, Photo

Set ContextLaunch

ConversationExtend OC Menus

Integrate Conversation

Window (WPF)Receive/Process

ContextUse Window Extension

Use Managed Client API to access conversation

Annotate Conversation

Save Conversation in your application

OR…build fully custom UI against the OC 14 Managed API

Before Conversation During Conversation After Conversation

IntroductionFeature overview

Integrating OC capabilities into your appDrag and drop Silverlight and WPF controls> Before the conversation starts…

> Find People People Search, Expert Search> Browse People Contact List, Custom List> View People Presence, Photo> Check Details Hover Card, Contact Card.

> Starting conversations…> Click to Call, IM, Video and Collaborate

> Default look and feel of OC 2010

Silverlight Controls

David OllasonLead Program ManagerOffice Communicator – Platform

demo

Integrating OC capabilities in your appDocking OC’s Conversation Window in rich Apps> Integrate the conversation window

itself…> Dock inside your Winforms or WPF app> Border is removed for a more integrated

feel> Size the window to appropriately fit your

app> Receive events and undock on resize> Conversation activity causes app to flash

in sys tray when minimized

Conversation Window Docking in a WPF Application

David OllasonLead Program ManagerOffice Communicator – Platform

demo

Making conversations contextualContext from Outlook today

> Do this, and more, from YourApp…

Sample Fill

Sender Receiver

Making conversations contextualPassing a simple link> A URL is programmatically passed

with the application invite to the receiver

> Subject of conversation can be set> Link appears in the conversation

history and receiver is invited to click “at own risk”

> No code is registered on receiver side

Contextual Conversations

David OllasonLead Program ManagerOffice Communicator – Platform

demo

Making conversations contextualPassing richer data – Sender-side> Sender-side programmatically sets:

> AppName – an identifier that the receiver uses to recognize the sender application.

> Program Launch link in addition to a simple URL. Sender enables receiver to click-to-launch a program locally.

> Include AppData in application invite. Constrained only by channel bandwidth

> Potentially instruct receiver to automatically open Conversation Window Extension

Making conversations contextualPassing richer data – Receiver-side> Receiver-side registers a package

that:> Matches AppName and establishes trust

with incoming invite> Can set contextual text in the invite

popup.> Inserts launch link / URL into conversation

history (no user warning necessary).> Receives and processes AppData> Can use Managed API to invoke

Conversation Window Extension> Can use API to dock conversation in WPF

app

Office Communicator extensibilityMenu extension points within OC

Main Window(right click menu)

Contact Card(overflow menu)

Shell execute My Application and pass Contact SIP URI(s)

Office Communicator extensibilityThe Conversation Window extension – features> A window attached to the right of the

conversation window.> Peer-to-peer communication (no

server-side BoT is required).> Hosts Silverlight natively, or a

browser.> Native Silverlight app has OC 14

Managed API access to the current conversation

Office Communicator extensibilityThe Conversation Window extension – invocation> Can be invoked in several ways

> Either user, independently, can invoke an app to run in the CWE from menu.> Menu contains apps registered for use in

CWE.> Sender’s invite can cause CWE to run

automatically on Receiver’s side.

Conversation Window Extension

David OllasonLead Program ManagerOffice Communicator – Platform

demo

The OC 14 Managed APIAPI access to UC capabilities> Fully Managed API adopting

standard .Net design patterns.> Bridge provides API access from

Silverlight> Requires Office Communicator and

leverages the same endpoint> Encompasses the functionality of both

IMessenger and UCCA> Underpins the Controls, Contextual

Conversations and Extensibility platform

The OC 14 Managed APIPublic interfaces

UCSignIn /

ClientConfig / Factory Methods

for Interfaces

UCUserOptions

Publishing Self-Presence / User

Options / Delegates

UCContacts/GroupsContact Management /

Groups / DG / Search / Presence / location

UCConferenceSchedule Conf/CAA

UCConversationIM / Audio / Video /

Conferencing

UCUtilitiesCall History / Missed Calls / Email / Tuning

Wizard

UIAutomationLaunch OC UI / Start

IM / Start File Transfer / Start App-

sharing / join conference

Public interfaces

The OC 14 Managed APIKey scenarios> Build conversation-aware applications

to run in the Conversation Window Extension

> Set context and build apps to receive and process context

> Build custom presentation UI and launch OC conversations

> Not for custom invites or conversation window while OC is visible, but…

> Fully suppress OC’s UI and build entirely custom UI against the API.

The OC 14 Managed APIKey scenarios

UIAutomation.StartConversation(                UiaConversationModes.InstantMessaging                , myParticipantList                , myContextTypes                , myContextObjects);

Write conversation-aware apps in the CWESuppress OC UI and

build custom standalone experiences

Use the API to launch OC from custom UI

Your Silverlight application can

run here and have API access to the

conversation

In Summary> Join Metro metroreq@microsoft.com

> Integrate Office-grade OC experiences into your applications

> Contextualize the invites sent from your applications

> Customize the OC experience during the conversation

> Build custom experiences against the OC 14 Managed API.

YOUR FEEDBACK IS IMPORTANT TO US! Please fill out session evaluation

forms online atMicrosoftPDC.com

Learn More On Channel 9> Expand your PDC experience through

Channel 9

> Explore videos, hands-on labs, sample code and demos through the new Channel 9 training courses

channel9.msdn.com/learnBuilt by Developers for Developers….

© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.