Simplified "Attach to Process" debugging

[Jim McKeeth 104]

It's been a long time since I've done much development with Windows services. I'm aware of the trick of creating a non-service version of the project, but sometimes that introduces subtle changes. I seem to remember a Host Application that would restart the service and then attach the debugger to the service. I know it is a little more complicated then that since you need to stop the service before compiling.

 

I imagine it worked something like this:

1. Run from IDE
2. Compiles
3. Automatically stops service
4. Links to EXE (or maybe it deployed it....)
5. Automatically restart service
6. Attaches debugger
7. Productivity

 

 

 

Is there a tool like this already? It might have been an in-house tool, or a fever dream.... All options are equally likely. If it was the latter two then I might try building it again.

 

Also, is there a list of macros like $(SanitizedProjectName) that are available in the IDE? I only found one mention of that one in the DocWiki, and that was only about a related bug fixes. There is the Transfer Macro list, but I believe some of those are specific to the Tool Properties, and it is still missing others like $(platform), $(target), etc. Completely unrelated, but there is a weird behavior I just noticed in the Tool Properties dialog. When you drop down the Macro's list, the edit boxes and labels all blank out. If you click the Insert button then it puts the dialog in a weird state too.

 

 

Thanks!

 

-Jim

Edited November 8 by Jim McKeeth

[Remy Lebeau 1392]

When I debug a service, I simply run the service normally in the SCM, and have its OnStart event pause execution until the debugger is attached.