1 / 35

The New Microsoft Communicator “14” SDK: Integrating, Extending and Adding Contextual Data to the New Communicator Exper

Required Slide. SESSION CODE : UNC322. The New Communicator “14” Platform. The New Microsoft Communicator “14” SDK: Integrating, Extending and Adding Contextual Data to the New Communicator Experience. David Ollason Lead Program Manager Microsoft Corporation. Agenda.

faolan
Télécharger la présentation

The New Microsoft Communicator “14” SDK: Integrating, Extending and Adding Contextual Data to the New Communicator Exper

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Required Slide SESSION CODE: UNC322 The New Communicator “14” Platform The New Microsoft Communicator “14” SDK: Integrating, Extending and Adding Contextual Data to the New Communicator Experience David Ollason Lead Program Manager Microsoft Corporation

  2. Agenda Key themes of Communicator “14” SDK • Integrate UC into your LoB applications • Making conversations contextual • Extending Communicator “14” with your applications • Building customized UI Migrating existing applications Summary

  3. Communicator “14” PlatformKey themes • IntegrateCommunicator Experiences • Add UC to your LoB Apps, like UC in Office • Contextual Conversations • Pass context of Application from Sender to Recipient • Extend Communicator Capabilities • Add custom Applications as extensions to Communicator • Custom Client UI • Build fully custom UI for standalone applications

  4. Integrate Communicator “14” experiencesSilverlight and WPF Controls Browse People Click to communicate Check details Find People Set personal status

  5. Integrate using Silverlight Controls Marcelo FarjallaProgram ManagerMicrosoft DEMO

  6. Integrate Communicator “14” experiencesConversation Window docking • Integrate the conversation window • 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

  7. Integrate Communicator’s Conversation Window Marcelo FarjallaProgram ManagerMicrosoft DEMO

  8. Contextual conversationsContext from outlook today • Do this, and more, from YourApp… Receiver Sample Fill Sender

  9. Contextual conversationsWith Communicator “14” platform Contextual data sent from your App. Simple Link is a URL within the trusted sites of the Enterprise Pass real data to be viewed by receiver. Program launch link receiver can click to launch same application as sender

  10. Contextual Conversations Marcelo FarjallaProgram ManagerMicrosoft DEMO

  11. Contextual conversationsPassing 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

  12. Contextual conversationsPassing 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

  13. Contextual conversationsPassing 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

  14. Extend the Communicator “14” experienceMenu extensibility Shell execute My Application and pass Contact SIP URI(s)

  15. Extend the Communicator “14” experienceConversation Window Extension • Launched by menu or programmatically:UIWindow.ShowExtensibilityWindow(…);

  16. Extend – Conversation Window Extension Marcelo FarjallaProgram ManagerMicrosoft DEMO

  17. Extend the Communicator “14” experienceConversation Window Extension (CWE) • A window attached to the right of the conversation window. • Peer-to-peer communication (no server-side BoT is required). • Hosts Silverlight application within a browser instance. • Silverlight app has access to Communicator 14 Managed API via Silverlight bridge.

  18. Extend the Communicator “14” experienceConversation Window Extension (CWE) • 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. • Can programmatically cause CWE to run on Sender’s side, Receiver’s side or both sides.

  19. Custom UI – re-templatingRe-templating the Controls • Support for re-templating via Expression Blend • Access to the XAML files • Alter or Extend the UI of any Communicator Control • Examples: • Add entry points into any application from within Communicator Controls • Alter “Look & Feel”

  20. Custom UI – Controls Re-templating Marcelo FarjallaProgram ManagerMicrosoft DEMO

  21. Custom UI – The Communicator “14” Managed APIAPI access to Communicator capabilities • Fully Managed .NET API • Easy access the underlying Communicator object model • Replaces W13 Client API’s – UCCA & Automation (aka. iMessenger) • API access via Silverlight • Re-uses the Communicator end-point (Communicator required) • Supports UI Suppression mode where Communicator is not desired • Platform upon which Controls, Contextual Conversation, Client extensibility is built

  22. Custom UI – The Communicator “14” Managed APIKey scenarios • Conversation window extension: Build conversation-aware applications to run in the Conversation Window Extension • Contextual conversations: Set context and build apps to receive and process the context • UI automation: Launch Communicator conversation window – IM, Audio/Video, App sharing, File transfer • Full UI suppression: Suppress Communicator and own the full user experience yourself

  23. Custom UI – The Communicator “14” Managed APIKey scenarios Your Silverlight application can run here and have API access to the conversation Write API-aware apps in the CWE UIAutomation.StartConversation( UiaConversationModes.InstantMessaging                 , myParticipantList                 , myContextTypes                 , myContextObjects); Security Kiosk is used by visitor to connect with employees running Office Communicator Suppress OC UI and build custom UI for standalone applications (For example, a security kiosk application) Use the API to launch OC from custom UI

  24. Custom UI – The Communicator “14” Managed APIPublic Namespaces • Microsoft.Communicator .Group .Model .Conversation.AudioVideo .Conversation Audio/Video Conversations Start Conversation/Instant Messaging/Participants/Conferencing Contact List/Group Management SignIn/Search/ContactInfo/Availability .Extensibility .Devices Communicator Automation/Extensibility/Contextual Conversations Audio/Video Device Management Public classes

  25. Silverlight Web App Desktop App (WPF) UI Controls (Silverlight and WPF) Contoso App .Model .Group .Extensibility .Conversation .Conversation.AudioVideo Communicator Automation/Extensibility/Contextual Conversations Contact List/Group Management SignIn/Search/ContactInfo/Availability Audio/Video Conversations Start Conversation/Instant Messaging/Participants/Conferencing Launch Communicator Communicator UI Automation Automation.StartConversation (AutomationModalitiesInstantMessaging,StringParticipantUris) No UI (Kiosk) Extension Model API Public classes

  26. Migration from 2007 R2 Name control (name.dll) • Encouraged to migrate to using the WPF and SL Controls for Presence and C2C integration. UC Automation & UCC API • UCC API to be deprecated after this release. In preparation for Wave 15: • Encouraged to migrate UCC API applications to the new Client Managed API. • Migrate UI Automation calls to their equivalent in the Client Managed API. UC Ajax APIs • These APIs are deprecated in W14: • Access UCMA via Web Services – sample on MSDN.

  27. Migration from 2007 R2Tab Applications in OC Main UI The Tabs area in the Main UI is being removed for Communicator “14”. • Contact List right-click menu is extensible – can add option to shell-execute MyApp. • MyApp is passed the Contact SIP URI of selected contact(s) • Works for single, multi and group selection. • Conversation window extension • Can add contact lists to 3rd party applications via controls.

  28. Communicator “14” PlatformSummary • IntegrateCommunicator Experiences • Use SL & WPF controls to add UC to your LoBApps. • Contextual Conversations • Use the Controls and the Managed API to contextualize conversations. • Extend Communicator Capabilities • Extend the Communicator “14” experience with your applications • Custom Client UI • Build fully custom UI for standalone applications • Migrate existing applications to the new platform.

  29. Required Slide Track PMs will supply the content for this slide, which will be inserted during the final scrub. Track Resources • Visual Studio – http://www.microsoft.com/visualstudio/en-us/ • Soma’s Blog – http://blogs.msdn.com/b/somasegar/ • MSDN Data Developer Center – http://msdn.com/data • ADO.NET Team Blog – http://blogs.msdn.com/adonet • WCF Data Services Team Blog – http://blogs.msdn.com/astoriateam • EF Design Blog – http://blogs.msdn.com/efdesign

  30. Unified Communications Track Call to Action! Learn More! • View Related Unified Communications (UNC) Content at TechEd/after at TechEd Online • Visit microsoft.com/communicationsserver for more Communications Server “14” product information • Find additional Communications Server “14” content in the Technical Library, weekly technical articles at NextHop, and follow DrRez on Twitter • Check out Microsoft TechNet resources for Communications Server and Exchange Server • Visit additional Exchange 2010 IT Professional-focused content • Partner LinkorCustomer Link (Name: ExProPword: EHLO!world) Try It Out! • Exchange 2010 SP1 Beta downloadis now available from the download center!

  31. Required Slide Resources Learning • Sessions On-Demand & Community • Microsoft Certification & Training Resources www.microsoft.com/teched www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers http://microsoft.com/technet http://microsoft.com/msdn

  32. Required Slide Complete an evaluation on CommNet and enter to win!

  33. Sign up for Tech·Ed 2011 and save $500 starting June 8 – June 31st http://northamerica.msteched.com/registration You can also register at the North America 2011 kiosk located at registrationJoin us in Atlanta next year

  34. © 2010 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.

  35. Required Slide

More Related