Summary

  • Direct input from and to a service from any user has to be designed carefully.

  • System output from a service to the desktop or workstation should be limited to situations with interactive users or imperative system events that must be visible to administrators.

  • When a service has privileges to interact with the desktop, any messages, boxes, or windows that require user interaction can be extremely dangerous if no user is currently logged on, or a user is logged on but away from his desk.

  • Never use forms in your services—they are never a supported strategy. User feedback should be provided through other notification channels such as the NT Event Log, Simple Network Management Protocol, SQL Server, SMTP, or any other logging mechanism.

Get Programming Windows® Services with Microsoft® Visual Basic® 2008 now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.