Sorry, I do not know is it valid topi or not so I put it here

  • Thread starter Thread starter IT Got
  • Start date Start date
I

IT Got

I have a service that need to communicate with currently logged interactive
on user, the service works under its own account.
I have a problem with displaying Dialog box to communicate with user, usage
of MessageBox does not resolve the problem, the dialog box has some
components that allows a user to make his choice.
If anybody know how to resolve the problem.
 
I believe it is true that service design requirements are
that a service should not present interactive user interface
elements and enter wait states due to them.
 
But we still have a MessageBox with a flag MB_SERVICE_NOTIFICATION that
allows us to show the dialog box.
By using this I did implement the solution that displays dialog box, hooks
it (adds some necessary components) and interracts with a user, but I deeply
fell that it is a bad practic....
 
I believe you will find it is definitely not a recommended practive.
You could look at a number of other approaches. A client side tool
that sets a reg value, and then signals the service or which the service
has evented for notification on change would be couple examples.
Read the docs at MSDN.microsoft.com as these will guide you,
but as I recall, one should not allow a thread of a service to enter
a state waiting on user interaction.
 
Back
Top