By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,823 Members | 756 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,823 IT Pros & Developers. It's quick & easy.

creating services with UI

P: n/a
Hi,

I would like to write a service in C# and I have the need to display a UI
with status information, statistics, etc. If I use the Windows Service
project in C#, I noticed that the System.Windows namespace is not available
to me in the intellisense when I type "using System.".

What is the recommended procedure in C# / .NET for creating services that
display UI's and need to allow interaction with the desktop?

Thanks in advace,
Arvind.
Jun 14 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
My suggestion would be your app consists of 2 pieces

the service, and an ui interface

the interace would just read log files / adjust settings etc

The service would write to the log file and read the settings

mike

mail.microsoft.com wrote:
Hi,

I would like to write a service in C# and I have the need to display a UI
with status information, statistics, etc. If I use the Windows Service
project in C#, I noticed that the System.Windows namespace is not available
to me in the intellisense when I type "using System.".

What is the recommended procedure in C# / .NET for creating services that
display UI's and need to allow interaction with the desktop?

Thanks in advace,
Arvind.


Jun 14 '06 #2

P: n/a

<mi***************@gmail.com> wrote in message
news:11*********************@f6g2000cwb.googlegrou ps.com...
My suggestion would be your app consists of 2 pieces

the service, and an ui interface
This is absolutely mandatory for security. Any application with a window is
no more secure than any other application with a window, because many
exploits are available using (for example) WM_TIMER.

the interace would just read log files / adjust settings etc

The service would write to the log file and read the settings
Better to use a TCP/IP socket with some form of password protection or
publickey/privatekey challenge. This gives you remote administration for no
additional effort.

If remote administration is not needed and you want Windows to handle
security, use a named pipe and set the ACL so that only administrators can
open it.

mike

mail.microsoft.com wrote:
Hi,

I would like to write a service in C# and I have the need to display a UI
with status information, statistics, etc. If I use the Windows Service
project in C#, I noticed that the System.Windows namespace is not
available
to me in the intellisense when I type "using System.".

What is the recommended procedure in C# / .NET for creating services that
display UI's and need to allow interaction with the desktop?

Thanks in advace,
Arvind.

Jun 14 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.