Posted by: rcosic | 14/02/2013

Migrate your code to Lync Client 2013

Hello everyone,

today I’ll write about on how to migrate your existing Lync 2010 code for usage with new Lync Server 2013.

Luckily, nothing much to be done here, since Lync Client 2010 API is fully compatible with the new server. Therefore, you can just start your application (whether it is a WPF controls / automation, or Silverlight CWA) and it should run smoothly. I have tested my existing integration project on different platforms using ‘old’ Lync Client 2010 API (I referenced namely Microsoft.Lync.Model.dll, Microsoft.Lync.Utilities.dll, and Microsoft.Office.Uc.dll) on several platforms (OS, processor, Lync server and client versions) and here are my findings:

- Vista 64bit (domain with Lync server 2010) – connecting to Lync client 2010 – both 32bit and 64bit apps works
– Win7 32bit (domain with Lync server 2010) – connecting to Lync client 2010 – 32bit works, 64bit don’t
– Win7 32bit (domain with Lync server 2010) – connecting to Lync client 2013 – 32bit works, 64bit don’t
– Win7 64bit (domain with Lync server 2013) – connecting to Lync client 2010 – both 32bit and 64bit apps work
– Win7 64bit (domain with Lync server 2013) – connecting to Lync client 2013 – 64bit works, 32bit don’t
– Win7 32bit (domain with Lync server 2013) – connecting to Lync client 2010 – 32bit works, 64bit don’t
– Win7 32bit (domain with Lync server 2013) – connecting to Lync client 2013 – 32bit works, 64bit don’t

I’ve also recompiled the project with new Lync Client SDK Preview, but it won’t work with Lync Client 2010 version, so I’ll skip it for the time being. New SDK can’t connect to the old Lync Client app, and our customers still use it, so I won’t be using it soon. But, it is worth noticing its potentials, especially if you plan to use some of the new features it has, such as:

- Resource sharing,
– Lync on-line meeting control, and
– Lync persistent chat room (previously: group chat) participation.

More info at: http://msdn.microsoft.com/en-us/library/lync/jj265327.aspx

The one thing that HAS changed with new Lync Client application is its process name. Previously, (from OCS version onward) it was named ‘communicator.exe’, and now, the client app is named’ lync.exe’. So, if you use some sort of tracking whether client process is running (as I do), make sure you update this functionality accordingly.

Kind regards,
Ratko.

About these ads

Responses

  1. nice post :), please visit back :D http://yosmantri.student.ipb.ac.id/2013/11/20/5-bacaan-wajib-seorang-programmer/ thanks :D


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: