"Angus" <anguscomber@gmail.com> wrote in message
news:1174651411.795153.258260@n76g2000hsh.googlegr oups.com...
in kernel groups.
Anyway, i would certainly ask here or in a Microsoft.* group.
the process and set breakpoints at appropriate locations. That has worked
for me when i once tried it. I guess you would like to start the process by
F10-single-stepping? You can't do that if you attach, you just have to
either attach fast enough or use command line trick to ensure you can catch
the breakpoint.
To specify the debugger as the ImagePath of the Service instead of the
service EXE, specifying it's path as a parameter:
ImagePath=c:\....path.to.devenv.exe c:\temp\debug\myservice\myservice.exe
This allows you to always start the debugger with the service start.
However, for debugging i find it much easier to make the EXE able to
interpret a commend line parameter that tells the process to run as a normal
(console) application and thus disable all SCM related code. This allows you
to debug the "payload" of the service and, usually, the service related code
is pretty much standard and shouldn't need much debugging.
- Sten
