Question

I have a Windows Service and I would like to see what it’s doing when it starts up. Normally to accomplish something like that, I’d hard-code a Thread.Sleep for like 10 seconds to give me enough time to attach the debugger. This is effective, but annoying, as I need to re-compile once to put the pause in and again when I (hopefully remember to) take the pause out. I know I could alternatively hard-code a break command in, but that also requires me to re-compile my solution.

I know I can also separate my service’s logic into a separate project that can be run in Visual Studio, which I can use most of the time, but sometimes I want to see exactly what my service is doing when it’s running as a service.

Is there a way that I can get my debugger attached to my service so that I can see the things it’s doing on startup, without hard-coding and re-compiling anything?

Answer 1

There is a registry key which gives you a chance to attach a debugger to the process as soon as it is created.

Save the following snippet as a *.reg file and import to your registry:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\services.exe]
"Debugger"="c:\\Program Files\\Debugging Tool For Windows\\windbg.exe"

remember to change ‘services.exe’ to the actual services executable file name.

You can also use the gflag tool to facilitate the work. For detailed information please check KB 824344: How to debug Windows services