While it CAN be done, it is not advisable. There is a possiblity of
priviledge elevation via windows message attacks (I don't know if .NET helps
with that or not, but is it worth the risk?).
If you must provide the UI from the service, use the most restrictive
possible user account for the service(Definatly not SYSTEM, LocalSystem,
Administrative accounts, etc, I'd say) lest someone trys to compromise it.
Also, I doubt it is as easy as running a simple winforms application
properly across TS. Client\server really makes more sense and is more
secure, plus it is probably easier to run the client code across multiple
accounts and should allow for remote administration as well(this may not be
a prime issue now, but you may need it at some point).
these urls may be of use as well:
http://support.microsoft.com/default...b;en-us;171890 http://support.microsoft.com/default...b;en-us;308403 http://support.microsoft.com/default...b;en-us;821794 http://support.microsoft.com/default...b;en-us;327618
"Action" <ac***************@hotmail.com> wrote in message
news:ew**************@TK2MSFTNGP09.phx.gbl...
I saw some service able to create a systray icon
or it user other shortcuts to do so..?
thx
"Daniel O'Connell" <on******@comcast.net> wrote in message
news:hAV7b.414938$Ho3.65699@sccrnsc03... A service, by default anyway, does not have access to your window
station, so it also doesn't have access to your system tray. You might be able to
work aroudn this with some creative p\invoke, but it wouldn't be highly
recommended.
To do what you want to do you will need to write a seperate application
that displays the system tray icon and communicates whatever is needed with
the service.
"Action" <ac***************@hotmail.com> wrote in message
news:uh**************@TK2MSFTNGP11.phx.gbl... I can add a systray icon in normal windows application...
but when i do it in windows service, the systray icon just don't show
up
is that because i don't have any "component" to contain the systray
icon? please give direction...
thx
