Messenger Library V2.0 migration to V2.5
As you may know, in recent months, we released Messenger Library (WLML) V2.0 (August 2008) and V2.5 (September 2008). V2.0 and V2.5 are very close feature-wise and we developed V2.5 to be fully backward compatible with V2.0. We are currently maintaining separate code bases for each version. As you can imagine, there is a high burden for maintaining two code bases for almost the same functionality.
Because of this, we plan to unify the code bases for V2.5 and V2.0, using the V2.5 code base for both. What this means for you is that you will continue to be able to load the library at both URLs (https://www.wlmessenger.net/api/2.0/messenger.js and https://www.wlmessenger.net/api/2.5/messenger.js) but they will point to the exact same code.
We are currently targeting this transition for 30 days from now. At a later date, we also plan to replace V1.0 with V2.5 as well.
We are already working with large partners to ensure that this transition will be smooth. We want to give everybody a heads up so you have the opportunity to try V2.5 before the transition, if you are using V1.0 or V2.0 in your application today.
Thanks,
Keiji
Comments
Anonymous
October 21, 2008
PingBack from http://blog.a-foton.ru/index.php/2008/10/22/messenger-library-v20-migration-to-v25/Anonymous
November 29, 2008
Is there something wrong with Messenger Live Services? From the MSDN site http://msdn.microsoft.com/en-us/library/cc298455.aspx, the live example accompanying the tutorial http://messenger.mslivelabs.com/samples/HelloWorld/JavaScript/WebSite/default.htm does not seem to work. I hope this will get fixed soon and I hope Microsoft will be very committed to the Windows Live Messenger Library and the Live services. Thank you.Anonymous
January 21, 2009
We posted a few months ago about our planned change to point Windows Live Messenger Library V2.0 to V2.5.