With the behavior change, an invalid index causes the ArgumentOutofRangeException exception to be raised. Collection class range exceptionsĬollection classes that implement the this property threw an IndexOutOfRange exception when an invalid index was specified. For information about subscribing to contact presence, see How to: Subscribe to enhanced presence content. To ensure that you get updated presence, maintain your own ContactSubscription for all contacts. If you want to continue to get presence publication notifications for out-of-view contacts, you must create and maintain a ContactSubscription object in your application logic.Ĭontacts that have been obtained from a search operation through the API are not contained in the subscription maintained by the Lync client. As contacts are scrolled out of view on the UI contact list, they are removed from the client-maintained contact subscription. The Lync 2013 client maintains a contact subscription for all contacts that are scrolled into view on the client UI contact list. The Lync 2013 API requires that every object that you want presence publication notification for is added to a before registering for the Contact.ContactInformationChanged event. Lync 2013 API code behavior changes are as follows: Contact presence subscription changes ![]() You can optionally install Silverlight 5 Tools for Visual Studio 2010 Service Pack 1.Ī code behavior change is a non-syntax API revision that changes the runtime behavior of a Lync 2013 API-based application. However, the Silverlight 5 runtime is required to support Conversation Window Extension applications and Persistent Chat window add-in applications that are hosted on Lync 圆4. Silverlight 4 Tools for Visual Studio 2010 is the minimal requirement for Silverlight development. If you develop Silverlight browser applications that use Microsoft Lync 2010 Controls and you are migrating these applications to Microsoft Lync 2013 Controls, you must download and install the following tools: For information about the new registry key, see Lync 2013 system registry keys. It gives explicit Lync 2013-access permission to Silverlight browser applications that are intended to extend Lync without giving the same permission to web sites and domains generally. The new key enables better security for the local Lync 2013 user. Silverlight browser applications for conversation window extension tabs and Persistent Chat Addin tabs require a dedicated local computer registry entry in a new registry key. Registry changes for conversation window extension applications The assemblies for Lync SDK have a default %Program Files%\Microsoft Office\Office15\LyncSDK\Assemblies\Desktop installation path.įor Silverlight applications, replace your existing Lync assemblies with the set of assemblies that are found in the %Program Files%\Microsoft Office\Office15\LyncSDK\Assemblies\Silverlight folder. Microsoft Lync 2013 SDK installs a new set of assemblies with the same names as the Lync SDK assemblies. Project changesįor Windows Forms or Windows Presentation Foundation (WPF) applications, you must replace the assembly that was installed with Microsoft Lync 2010 SDK. ![]() Be sure to uninstall previous versions of the runtime on computers that host your application. ![]() Microsoft Lync 2013 SDK includes a new redistribution application (redist.msi) that installs a new version of .dll that supports your Lync 2013 API-enabled application. A side-by-side installation of the SDK versions might not destabilize your applications but it is not supported by Microsoft. The assemblies, samples, and documentation are installed in different folders but the .dll for both versions of the SDK is installed in the Global Assembly Cache. If you have installed Microsoft Lync 2010 SDK on your computer, you should uninstall it before you install Microsoft Lync 2013 SDK. For information about these changes, see the Code behavior changes section.Īdd new Lync SDK features to your application by using the classes and types described in What's new in Lync 2013 SDK. There are API behavior changes that you should be aware of. No code changes are required to recompile your existing Lync SDK-enabled application that references the Lync SDK assembly. The migration tasks include changes to assemblies that are referenced in your project and the installation of the latest Microsoft Silverlight development support tools. Learn how to migrate your existing Microsoft Lync 2010 SDK-enabled application to Microsoft Lync 2013 SDK.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |