Monitoring a service works for:
•mixed mode services.
If you are working with native services you must use the NT Service API in your service as well as using the Monitor a service method below.
Bug Validator won't attach until some .Net code is executed.
If there is native code being called prior to the .Net code, Bug Validator won't monitor that code, only the native code called after the first .Net code that is called.
To monitor any native code called prior to your .Net code, use the NT Service API.
When working with Bug Validator and services, you still start the service the way you normally do - e.g. with the service control manager.
The code that you have embedded into your service then contacts Bug Validator, which you should have running before starting the service.
To start monitoring a service:
or use the shortcut
Monitor a service
First ensure the service is installed, but not running.
Set the service to monitor, choose whether to start collecting data right away, and click OK.
•Service to monitor type or Browse to set the service name to monitor
•OK waits for the service to start before injecting into it
Start the service in the normal manner, e.g. from the control panel, the command line or programmatically.
Depending on your application, and what you want to validate, you may want to start collecting data as soon as injection has happened, or do it later.
If your program has a complex start-up procedure, initialising lots of data, it may be much faster not to collect data until the program has launched.
If it's the startup procedure you want to validate, obviously start collecting data immediately.
Example demonstrating how to monitor a service.
Example demonstrating how to monitor an application launched from a service (how to monitor any application running on a service account).