We are trying to write a simple GUI front end to communicate with a service.
We need the GUI to make the service fire certain events if the user needs to
re-perform certain tasks manually, and possibly return a result string with
back to the user from what the service did, records processed, errors, etc.
We are thinking there should be a system tray icon as well that the user
uses to open the GUI as needed.
We tried to keep it simple, and just make a service out of our existing GUI
form, and set it to interact with the desktop. Apparently, right click menus
do not work with system tray service apps, and the icon itself doesn't go
away as expected when the app shuts down. All in all, not a very elegant,
stable or confidence inspiring solution.
We then tried to make a separate GUI app, and keep all UI out of the
service. The process controller I think we can only SEND integer commands,
so it is not really powerful enough.
Should we be looking at remoting? Is there an easier way? We have been
through a half dozen examples on MSDN, various articles, etc. and by the
time we try to put a remoting sample together with a service example with a
system tray icon example, then get all the .dll's created, build an install
program, then try to get it installed on a test machine it all falls apart.
Any ideas on this? We have been doing stuff like this for years with pre-dot
net versions of VC, but just can't get our heads around doing it now with
..NET.
Thanks....
|
Similar Threads
