IMessengerAddIn deprecated?

[Yakker]

the messenger addin documentation available at...
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/WinMessenger/winmessenger/messenger_entry.asp

says that the IMessengerAddIn is deprecated as are the
IMessengerAddInManager and several other of the associated interfaces.
why were they deprecated? are there new interfaces to take their
place?

[Jonathan Kay [MVP]]

Greetings,

The latest Windows Messenger (5.0) no longer has support for Add-Ins and as far as I know,
there isn't anything to take their place.
____________________________________________
Jonathan Kay
Windows MVP, Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com

"Yakker" > wrote in message
om...
> the messenger addin documentation available at...
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/WinMessenger/winmessenger/messenger_entry.asp
>
> says that the IMessengerAddIn is deprecated as are the
> IMessengerAddInManager and several other of the associated interfaces.
> why were they deprecated? are there new interfaces to take their
> place?

[Yakker]

>
> The latest Windows Messenger (5.0) no longer has support for Add-Ins and as far as I know,
> there isn't anything to take their place.

thanks for your reply. that is interesting. perhaps they recognized
that this api gave 3rd party developers too much control to build
disruptive p2p applications on top of msft's investment.

[Jonathan Kay [MVP]]

Hi Yakker,

To be honest, I think that it just wasn't used enough to warrant supporting it (don't take
this as an official response, just personal opinion).
____________________________________________
Jonathan Kay
Windows MVP, Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com


"Yakker" > wrote in message
om...
> >
> > The latest Windows Messenger (5.0) no longer has support for Add-Ins and as far as I
know,
> > there isn't anything to take their place.
>
> thanks for your reply. that is interesting. perhaps they recognized
> that this api gave 3rd party developers too much control to build
> disruptive p2p applications on top of msft's investment.