- .NET Messenger Service
The .NET Messenger Service (formerly MSN Messenger Service [http://www.microsoft.com/presspass/press/1999/jul99/messagingpr.mspx Microsoft Launches MSN Messenger Service] ] and sometimes called Windows Live Messenger Service [http://support.microsoft.com/gp/Messenger Microsoft Help and Support: Important changes to Windows Live Messenger] ] ) is an
instant messagingand presence system developed by Microsoftin 1999 for use with its MSN Messenger software and used today by its current instant messaging clients, Windows Live Messengerand Microsoft Messenger for Mac. Third-party clients also connect to the service. It communicates using the Microsoft Notification Protocol, a proprietary instant messaging protocol. The service allows anyone with a Windows Live IDto sign in and communicate in real time with other people who are signed in as well.
Despite multiple name changes to the service and its client software over the years, the .NET Messenger Service is often referred to colloquially as "
MSN," due to the history of MSN Messenger. The service itself was known as MSN Messenger Service from 1999 to 2001, at which time, Microsoft changed its name to .NET Messenger Service and began offering clients that no longer carried the "MSN" name, such as the Windows Messengerclient included with Windows XP, which was originally intended to be a streamlined version of MSN Messenger, free of advertisements and integrated into Windows. [http://www.microsoft.com/windowsxp/using/windowsmessenger/getstarted/intro.mspx Get Started with Windows Messenger v4.0] ]
Nevertheless, the company continued to offer more upgrades to MSN Messenger until the end of 2005, when all previous versions of MSN Messenger and Windows Messenger were superseded by a new program,
Windows Live Messenger, as part of Microsoft's launch of its Windows Liveonline services.
Currently, the official name for the service remains .NET Messenger Service, as indicated on its official network status web page, [http://help.live.com/help.aspx?project=wl_messengerv1_1&market=en-us&querytype=topic&query=messenger_proc_checkmessengerservicestatus.htm Check the Microsoft .NET Messenger Service status] ] though Microsoft rarely uses the name to promote the service. Because the main client used to access the service is called
Windows Live Messenger, Microsoft has recently started referring to the entire service as the Windows Live Messenger Service in its support documentation.
The service can integrate with the Windows
operating system, automatically and simultaneously signing into the network as the user logs into their Windows account. Corporations can also integrate their Microsoft Office Communications Serverand Active Directorywith the service.
Microsoft offers the following instant messaging clients that connect to the .NET Messenger Service:
Windows Live Messenger, for users of Microsoft Windows
**MSN Messenger was the former name of the client from 1999 to 2005
Windows Messengerwas a basic version of the client included with Windows XPin 2001
Microsoft Messenger for Mac, for users of Mac OS X
*MSN Web Messenger, a
web browser-based messaging program for use through Internet Explorer
Windows Live Web Messengeris in development now and will soon supersede it
Additionally, these third-party clients and others can access the .NET Messenger Service:
Adium(Mac OS X, GPL)
*Agile Messenger (S60 and
Windows Mobile, proprietary, commercial)
BitlBee(Windows and Unix-like, GPL)
Digsby(Windows, Mac and Linux planned, proprietary)
*eMSN (Mac OS X)
eBuddy(Web-based and Mobile)
*Fire (Mac OS X, GPL)
Jabber(Any client supporting Jabber protocol can use transports to connect to .NET Messenger Service)
KMess(Linux KDE, GPL)
Kopete(Linux KDE, GPL)
Miranda IM(Windows, GPL)
Mercury Messenger(formerly dMSN) (Multi-platform, proprietary)
*Pidgin (formerly Gaim) (Multi-platform, GPL)
*Shape Services IMPlus (S60)
tmsnc(Multi-platform, text based)
*Trillian (Multi-platform, Web, proprietary)
Windows NT Messenger Service
Windows NTand newer operating systemsfrom Microsoft included a system notification service called Messenger service, which was intended for use within workgroups, but eventually became used maliciously to present pop-up advertisements to users. This service, although it has a similar name, is not related in any way to the .NET Messenger Service or the Windows Messengerinstant messaging client. It became disabled by default with Windows XP Service Pack 2 and Windows Server 2003 Service Pack 1 and was removed completely in Windows Vistaand Windows Server 2008.
Microsoft .NET Framework
Despite its name, the .NET Messenger Service is not in any way related to the
Microsoft .NET Frameworkdevelopment platform. Neither the official clients nor the protocol itself is tied to the .NET Framework.
Windows Live Messenger
Microsoft Messenger for Mac
Windows Live ID
Microsoft Notification Protocol
Comparison of instant messaging clients
Comparison of instant messaging protocols
* [http://messenger.msn.com/Status.aspx .NET Messenger Service Status]
* [http://messenger.live.com/ Windows Live Messenger]
* [http://webmessenger.msn.com/ MSN Web Messenger]
* [http://messidog.live.com/ Windows Live Web Messenger]
* [http://www.hypothetic.org/docs/msn/ MSN Messenger protocol documentation]
* [http://msnpiki.msnfanatic.com/ MSNPiki (protocol wiki)]
Wikimedia Foundation. 2010.