Note: this post is part of Lync Client development series. You can find the following topics here:
- Microsoft Lync Client Development,
- Sign in and out in Microsoft Lync Client,
- Lync Controls inside Lync Client SDK,
- Starting with Lync Client’s API,
- Handling some common scenarios with Lync Conversation,
- Handling transfers in Lync Client API,
- Handling conference calls in Lync Client,
- Availability (presence) in Lync Client.
after a while I’m back with blogging. In the next period of time, I’ll try to give you my feedback on a various development themes, especially in doing research and development for Microsoft Lync Client. I will try to do the best I can to convince you that it is not so hard, along with my impressions about the Lync, Client API and the general subject.
To start, here is what you need to start developing for Microsoft Lync 2010 on a client side:
- Microsoft Lync Client 2010 x86 or x64,
- Visual Studio 2010 (I’m using Premium version),
- Silverlight 4 Tools and Silverlight 4 Toolkit (April 2010) – if you are customizing a conversation window,
- Lync Client SDK (this is a MUST),
- and a couple of small tools, on a server or client to track the sip line (this one will be explained in some future post).
So, to begin, you install all these stuff, and start the Visual Studio 2010. When you open a new project, you’ll have two new project templates available:
- Lync Silverlight application, and
- Lync WPF application.
With these, you’ll get the assemblies ready to use on each of the platforms, namely:
As for the style of development, you can choose whether you want to consume the existing Lync controls that come out of the box, and/or use Automation objects to simulate the actions Lync Client does. Also, you have the opportunity to enhance the conversation window (the window that pops up on the screen when a conversation starts) – creating a context-based conversations.
So, common scenarios would be to create an extension to an existing Lync system for your company, in which you will present an additional context besides each conversation you made. Or you can integrate the existing call center solution with Lync in a more complex way (this is something I’m doing right now). Either way, there are vast of possibilities, but also many limitations of using Lync Client API (some of them I will present in the following posts).
There are many samples on the web regarding Lync Client API, but most of the samples don’t really dive in into the development. So, I will try to correct this fact.