Shoutbox

quote:

---

Originally posted by deAd
The API can be used with the ActiveXControl object.

code:

---

var MessengerAPI = new ActiveXObject("Messenger.UIAutomation.1");

---

This might not work on all machines, and some features (like groups) will not be accessible/may crash wlm.

---

Never use the ".1", ".2" or whatever as a reference. This is part of the reason why it doesn't work on some machines. Those identify the versions so to speak, of the activex objects. Specifiying them will cause Windows quite often to not find the proper 'versions'.

see CookieRevised's reply to [Question] Any way I can get a Winsock ActiveXObject working ?

Also note that each time you use 'ActiveXObject("Messenger.UIAutomation")' a new object is created which will lead to out of memory problems, and maybe even crashes, etc very rapidly.

Hence, I suggest to not use this in scripts...

related:

http://forum.mess.be/index.php?s=73b0a25dcb617f93...5b&showtopic=19108
http://forum.mess.be/index.php?showtopic=55 (<= SpunkyLoveMuff, read this also)
http://forums.fanatic.net.nz/index.php?showtopic=5799
http://www.devhood.com/tutorials/tutorial_details.aspx?tutorial_id=478

quote:

---

Originally posted by SpunkyLoveMuff
I've been working in VB6 all night figuring out the API commands so I could write a DLL to use or something. That seems likes a good solution that you posted, but why does it make Messenger run in the background?

---

If you want to use a DLL, you don't need what has been posted before. See forums like MSNFanatic for more info on how to create a DLL which references the Messenger API.

Or you can also find a lot of examples in the plugins section on this forums.

Also, in VB6, you can use the object browser to get all the available objects, properties, functions, etc at your disposal (after you have created a reference  to the Messenger API).

quote:

---

Originally posted by CookieRevised

quote:

---

Originally posted by deAd
The API can be used with the ActiveXControl object.

code:

---

var MessengerAPI = new ActiveXObject("Messenger.UIAutomation.1");

---

This might not work on all machines, and some features (like groups) will not be accessible/may crash wlm.

---

Never use the ".1", ".2" or whatever as a reference. This is part of the reason why it doesn't work on some machines. Those identify the versions so to speak, of the activex objects. Specifiying them will cause Windows quite often to not find the proper 'versions'.

---

I am aware of that, but I do not know of another working ID...so I posted that and a warning ...

quote:

---

Originally posted by deAd

quote:

---

Originally posted by CookieRevised

quote:

---

Originally posted by deAd
The API can be used with the ActiveXControl object.

code:

---

var MessengerAPI = new ActiveXObject("Messenger.UIAutomation.1");

---

This might not work on all machines, and some features (like groups) will not be accessible/may crash wlm.

---

Never use the ".1", ".2" or whatever as a reference. This is part of the reason why it doesn't work on some machines. Those identify the versions so to speak, of the activex objects. Specifiying them will cause Windows quite often to not find the proper 'versions'.

---

I am aware of that, but I do not know of another working ID...so I posted that and a warning ...

---

The working* id is without the ".1". See link** in previous post why

* though I wouldn't call it 'working'. See also previous post

** CookieRevised's reply to [Question] Any way I can get a Winsock ActiveXObject working ?

Just one more silly question I promise

IS this all the decumentation on messengerAPi or is there anything else?

Documentation I found

Thanks

quote:

---

Originally posted by Matty

quote:

---

Originally posted by SpunkyLoveMuff
why does it make Messenger run in the background?

---

It is a bug in Windows XP where the API, if Windows Messenger is installed, is run because natively Windows XP uses the API for certain features like Remote Assistance.

---

Its not really a bug though, its more how it is designed...

For a very detailed explanation, see:
http://www.fanatic.net.nz/2006/03/22/msn-messenge...api-confusion.html

quote:

---

Originally posted by Deco
Just one more silly question I promise

IS this all the decumentation on messengerAPi or is there anything else?

Documentation I found

---

Not a silly question though...

The link you provided is a part of the documentation, the main link is this one.

Go to there you'll also see that this documentation is very old and actually meant for Windows Messenger, not MSN Messenger, let alone for Windows Live Messenger.

That same documentation is also available as a chm file though (somewhere, don't have the link at hand).

But many things stated there still apply or can be taken as basis. More details and practical examples can be found on various forums (msnfanatic, mess.be, this one, etc).




* for SpunkyLoveMuff and others who want to make a DLL which references the Messenger API, see sites as MSNFanatic, mess.be, etc. eg:

More (unofficial) info and examples on the Messenger API:
http://www.fanatic.net.nz/2003/05/31/introduction...-type-library.html
http://www.fanatic.net.nz/2004/08/02/display-picture-api.html
http://www.fanatic.net.nz/2005/10/10/accessing-an...-contact-list.html



* Related API docs (official):
Windows Live Messenger development
Messenger Activity Add-In API documentation 1
Messenger Activity Add-In API documentation 2
Yahoo Messenger API documentation

You're my hero Cookie.

Much love.

quote:

---

Originally posted by Matty
MessengerAPI.InstantMessage('johndoe@hotmail.com');

---

but what if a function returns an object? in vb this would be

code:

---

Dim contact As IMessengerContact
contact = MessengerAPI.GetContact("email")

---

Just the same, only it's

code:

---

var Contact = MessengerAPI.GetContact("email")

---