Lync Controls architecture

Lync 2013

Core concepts

Learn about the basic process architecture of the Microsoft Lync 2013 Controls and their relation to the Microsoft Lync 2013 client application.

Last modified: February 22, 2013

Applies to: Lync 2013 | Lync Server 2013

Each Microsoft Lync Controls application connects to Lync Server 2013 using a single out-of-process connection to Microsoft Lync 2013. The application is either a Microsoft Windows Presentation Foundation (WPF) or Microsoft Silverlight application containing Lync Controls. The application’s connection to Lync 2013 is created by the first Lync Control instantiated by the application. This first control configures the layer between Lync 2013 and the application. Figure 1 illustrates the relationship between a Lync 2013 Controls-based application and the Lync 2013 SIP endpoint of the Lync Server 2013.

The first instantiated Lync Control automatically performs the following tasks:

  • Adds Lync 2013 connectivity to a WPF or Silverlight application without requiring code-behind.

  • Allows use of multiple interfaces between Lync Controls and Lync 2013 in a single application.

  • Handles and exposes runtime errors.

  • Ensures shutdown of the layer between the Lync Controls application and Lync 2013.

Figure 1. Lync controls architecture

Shows SL and WPF pages + Lync controls use server

Each subsequent Lync Control opened by the application uses the existing connection. Because all Lync Controlscan perform initial tasks, you can focus on putting only the controls that implement the Lync features that you need on a window. In addition, you do not write any client-side initialization code.

To get the connection state, check the following properties:

For more information about checking connection state, see Troubleshooting Lync Controls applications.