Comments on: MSN Messenger vs. Windows Messenger API confusion

By: bali

bali — Tue, 27 May 2008 09:32:02 +0000

tuk tuk

By: Paul Smith

Paul Smith — Fri, 09 Nov 2007 19:31:24 +0000

my wife and kids were using MSN Messenger but it has been unuseable for some time now. The problem seems to be when we try to sign into MSN Messenger there is an indication that a newer version (7.5) which must be loaded (upgraded to) in order to complete sign in. I have been unable to complete this upgrade. The download seems to go OK and the installation process stalls at a certain point and I have to end the process. I have tried removing all the MSN Programs and reinstalling them by I am just going around in circles. If you have any suggestions to keep my computer from taking that flying leap across my backyard, I would be grateful.
Thanks, Cheers
Paul Smith

By: Jim

Jim — Thu, 05 Apr 2007 23:06:51 +0000

Thanks for the great advice on how to turn off messanger!

Jim

By: Creating an IM Object Model : Visual Studio SDK

Creating an IM Object Model : Visual Studio SDK — Mon, 02 Apr 2007 23:38:46 +0000

[...] Abstracting Live MessengerWith core functionality taken care of, attention can then shift to the underlying implementation interfaces for Live Messener to create a ‘concrete’ first implementation of our ‘Instant Messenging’ functionality. As mentioned in a previous post, there’s a hefty amount of interaction and coupling that goes on between Windows Messenger and MSN/Live Messenger. As such, the cleanest way to implement Messenger functionality, at this point, is to use Interop Interfaces that tie in directly against Windows Messenger functionality. (After a bit of testing, I was able to verify that these interfaces are installed with Live Messenger 8.1 on both Windows XP and Windows Vista.) To test this out your ability to leverage these APIs, you can easily just add a new COM reference in Visual Studio, browse to the location where msmsgs.exe is located, and add it. If you do so, you’ll see that Visual Studio imports 3 new namespaces, or COM Interop assemblies for you - one for each of the type-libraries exposed by Windows Messenger. (Live Messenger exposes similar interfaces - but uses a different object model that I wasn’t able to easily ‘tap into’). But, to implement our needed functionality for this project we only need one of those three interfaces. (Likewise, when it comes time to ‘bundle’ this COM Interop assembly with our VSPackage we’ll see that it needs to be strongly named - or signed. Rather than using Visual Studio to import the Messenger Type Libraries, I therefore opted to just do it manually - using tlbimp.exe. Only, if you fire tblimp.exe against msmsgs.exe you only get back a single Interop Assembly (which happens to be one of the two that isn’t needed for this project). It turns out that, in the COM world, you need to explicitly specify which interface you want to import when there are multiple interfaces (or Type Libraries) ‘nested’ within a single COM assembly. To do that you you just need to use n syntax - where the n represents the ordinal number of the Type Library/Interface that you wish to consume (hat tip: Allen Denver). [...]

By: Leveraging Windows Live Messenger : vssdk.com

Leveraging Windows Live Messenger : vssdk.com — Thu, 29 Mar 2007 15:57:17 +0000

[...] So, for our first VSSDK project, we’re left dealing directly with the Messenger APIs themselves - which really aren’t documented very well, and are subject to a certain degree of mystery and change. Happily I was able to find a very enlightening overview of some of the issues associated with working with Messenger (warning: that link isn’t for the faint of heart *grin*). If you don’t have the time, patience, or inkling to read that link just know that the ‘moral of the story’ of working with Messenger is that you shouldn’t really bind any logic directly to it. In other words, we’ll be using an Adapter Pattern as part of our underlying ‘Messenging’ functionality in the first VSSDK project. Of course, that ends up working out fine - as we also want to remove any underlying dependence upon a particular platform. [...]

By: Meri

Meri — Sat, 02 Sep 2006 02:51:47 +0000

I have MSN Messenger 7.5 and would like to know if this is the latest version or if there is a new one. If there is an update, where do I find it? Thanx!

By: nick zello

nick zello — Tue, 15 Aug 2006 17:45:02 +0000

I was recently switched from msn hotmail to windows beta. How do I get msn back?

By: Tim

Tim — Mon, 17 Jul 2006 13:31:13 +0000

Tell me please, can I use Interop.MessengerAPI.dll not using Windows Messenger. I can register it manually. But I wonder if there any problems about that.

By: Dalin

Dalin — Tue, 11 Jul 2006 21:49:22 +0000

Windows Messenger had many security issues and if uninstalled properly, it won’t interfere with the usage of the API at all.

By: Blackice’s Blog » MSN and Weather Report V2 Previews are up!

Blackice’s Blog » MSN and Weather Report V2 Previews are up! — Sun, 28 May 2006 02:33:21 +0000

[...] Leave any feedback as a comment here, and I’ll take a look at it. The MSN one is XP-only, due to Microsoft screwing around with the Windows Messenger/MSN Messenger APIs. Basically, read this. [...]