[?] Messenger Client - Printable Version
-Shoutbox (https://shoutbox.menthix.net)
+-- Forum: MsgHelp Archive (/forumdisplay.php?fid=58)
+--- Forum: Messenger Plus! for Live Messenger (/forumdisplay.php?fid=4)
+---- Forum: Scripting (/forumdisplay.php?fid=39)
+----- Thread: [?] Messenger Client (/showthread.php?tid=76615)
[?] Messenger Client by Spunky on 08-08-2007 at 12:17 AM
Is there anyway to access the messenger client directly through a script rather than using the function provided by Plus?
For example I want to access function like: MessengerClient.SendTextMessage(txt, recipient)
but also others as well.
Is it possible or does it need to be a program?
RE: [?] Messenger Client by deAd on 08-08-2007 at 01:00 AM
MessengerClient is only for add-ins.
RE: [?] Messenger Client by Spunky on 08-08-2007 at 01:10 AM
quote:
Originally posted by deAd
MessengerClient is only for add-ins.
So it would have to be an exe? (similar to how plus works I guess)
quote:
Originally posted by markee
Isn't this possible through an ActiveXObject or was that only with previous versions of Messenger? I don't know the limitations on it however (like what is available to be used and stuff).
You can access messenger, but I'm not sure about the WLM control. I used ActiveX to get stuff from messenger in the past though
RE: [?] Messenger Client by markee on 08-08-2007 at 01:10 AM
Isn't this possible through an ActiveXObject or was that only with previous versions of Messenger? I don't know the limitations on it however (like what is available to be used and stuff).
RE: [?] Messenger Client by vikke on 09-17-2007 at 04:12 PM
In previous versions of Windows Live Messenger, there were a hidden feature (that required registry changes to show up). This feature allowed developers to develop their own "add-ins" using this API in dotNet. However the feature was removed not so long ago. You cannot access it from scripts neither from DLLs or EXEs.
Stuffplug 3 had a feature to enable this API to non-dotNet applications, but that feature was also removed due to security reasons.