When a resource control action is available, the methods that you invoke to take an available action are exposed on the ApplicationSharingModality object.
Working with sharing conversation modality objects To refresh a shareable resource list, you must read the ShareableResources property. You are not notified when new processes are started after the application sharing modality is connected. Maintaining a list of locally shareable resourcesĪ locally shareable collection of resources includes the desktop, monitors, and any UI-based processes that are running when a conversation is started and the conversation application sharing modality is connected. A resource viewer is a presenter or attender who is viewing a resource shared by a different conversation participant. TipĪ resource sharer is a conversation presenter who is sharing a local resource with other conversation participants. For example, if a running process has a UI with a Close button, the controlling user can click the button with the controlled mouse and close the process. Resource control amounts to giving the controlling user access to the local mouse and keyboard in the context of the shared resource.
The shared conversation resource can be controlled by one user at a time. It is only when the control of the resource is given to another user that the resource is considered controlled. A shared resource that is under the control of the resource owner is not considered controlled. In addition, only one conversation participant can share a resource at a time. Although a computer can have any number of shareable resources, only one of these resources can be shared in a conversation at a time. The Lync 2013 API does not support resource sharing when Lync 2013 is running in UI suppression mode.Ī shareable resource can be the local desktop, any display attached to the local workstation, or a running process such as Notepad.exe.
Most of the code that you write for resource sharing handles events on the sharing modalities. Shareable resource objects such as a running process or desktop.Įach of these objects expose methods, events, and properties that you use to manage the resource sharing process. In general, you program by using the following kinds of Lync 2013 API objects: Lync client sharing stage with running process When another user is granted control of a locally shared resource, the controlling user has the same access to the content within the resource that the owner does.įigure 1. A user must be aware that sensitive information can be seen by other participants when a resource such as a desktop, running process, or display is shared. CautionĪ shared resource is visible on the sharing stage for all conversation participants to view. Figure 1 shows a running process shared on the Lync 2013 sharing stage and visible to all conversation participants. The .Sharing namespace contains the classes and enumerations that you use in resource sharing.
However, you can use the API to build programmatic control over the sharing stage of the conversation window. The Lync 2013 API does not provide a control that you can drop into your application UI. The only way for a user to see shared resources in a conversation is to open a Lync 2013 conversation window on the desktop. Microsoft Lync 2013 SDK lets you start system resource sharing and manage user control of a shared resource on the sharing stage of a Microsoft Lync 2013 conversation window. Learn about programmatically sharing a computer monitor, desktop, or running program with another Microsoft Lync 2013 user in a conversation window by using classes in Microsoft Lync 2013 SDK.