Controlling CWEs and Notifications in Lync 2010 Contextual Conversations: Desktop Applications (Part 3 of 3)

Summary:   This article describes how to add three registry entries in various combinations to control the display of the Conversation Window Extension (CWE) and the start link notification in a Microsoft Lync 2010 contextual conversation.

Applies to:   Microsoft Lync 2010 | Microsoft Lync 2010 SDK

Published:   January 2012 | Provided by:   John Clarkson, Microsoft | About the Author

Contents

• Introduction

• Part 1 and 2

• Conclusion

• Additional Resources

Introduction

A desktop contextual application in this context is a Lync Windows Presentation Foundation (WPF) or Lync Model API application, or a C++ application that uses Office integration through the COM layer.

The examples in part 3 use simple WPF applications that have unique content in the Image and Label controls to visually distinguish the applications on the two computers. The Lync WPF application on the sending computer includes a StartInstantMessagingButton control that starts the conversation.

To include the start link notification

1. When registering the desktop application, include the Path entry as shown in figure 1.

   Figure 1. Registry

   

2. Start the conversation. In figure 2, the conversation window opens and includes a start link notification.

   Figure 2. Conversation window and application

   

3. On a computer that receives the message, click the invite. The conversation window opens and includes the start link notification. To open the contextual application, click the start link appearing in figure 3.

   Figure 3. Conversation window and application

   

To start a conversation that excludes a start link notification

1. When registering the desktop application, do not include the Path entry as shown in figure 4.

   Figure 4. Registry

   

2. Start the contextual conversation. In figure 5, the conversation window opens and it excludes a start link notification.

   Figure 5. Conversation window and application

   

3. On a computer that receives the message, click the invite and the conversation window opens, as shown in figure 6. The start link is not displayed. Open the contextual application through another process.

   Figure 6. Conversation window

   

Part 1 and 2

• Controlling CWEs and Notifications in Lync 2010 Contextual Conversations: Introduction (Part 1 of 3)

• Controlling CWEs and Notifications in Lync 2010 Contextual Conversations: Silverlight Applications (Part 2 of 3)

Conclusion

Use the three registry entries that control the application path and the URL to control whether the CWE opens and whether the start link notification appears in the conversation window. The three registry entries:

• Path

• InternalURL

• ExternalURL

Including these entries in different combinations when you register a contextual application determines whether the start link and CWE appear in a conversation.

Additional Resources

For more information, see the following resources:

• Lync Developer Center

• Application Registration for Lync 2010 Contextual Applications

• Register Contextual Conversation Packages in Lync 2010

• Walkthrough: Perform Install Registration for an Extensibility Application (Lync 2010 SDK)

• Walkthrough: Perform Run-Time Registration for an Extensibility Application (Lync 2010 SDK)

About the Author

John Clarkson is a programming writer with the Microsoft Lync product team.