>Isn’t the MMC plug in architecture how UI’s for services are really
supposed to be designed now?
Yes.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Jan Bottorff
Sent: Sunday, December 16, 2001 11:15 AM
To: NT Developers Interest List
Subject: [ntdev] RE: NT Service showing icon in systray
I’d agree with JK’s opinion, not having a service interact with the desktop
is an especially good idea as of WindowsXP (and Terminal Services). In
WinXP Pro, you can have multiple interactive sessions, so WHICH desktop
should the service interact with.
I think a much better architecture is to have a service, and ALSO have an
interactive UI application that talks to the service through some
appropriate communication channel (like TCP/IP, or if memory serves me, a
COM singleton object). If you want, the UI app can be in the system tray of
the local machine.
Isn’t the MMC plug in architecture how UI’s for services are really
supposed to be designed now?
As a good rule, never use the interact with desktop flag and never tyr
to use Gui or MFC in a service.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Shrishail Rana
Sent: Sunday, December 16, 2001 8:26 AM
To: NT Developers Interest List
Subject: [ntdev] NT Service showing icon in systray
I have a problem. How a service can interact with desktop and install
icon in system tray. Here are the functions that are used to allow a
service to interact with desktop. I got them from a service complied
file. The Service shows an icon in the system tray. It uses following
function in this order.
You are currently subscribed to ntdev as: xxxxx@youngendeavors.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com