Comments on: How To Make Debugging .NET Windows Services Easier

By: cs

cs — Fri, 25 Jan 2008 15:48:44 +0000

Hi, nice tip because it also works on ViSTA 64. For now

I’ll keep using the Debugger.Launch() trick (http://www.duelec.de/blog/?p=58)

By: jfrankcarr

jfrankcarr — Tue, 30 Oct 2007 13:37:32 +0000

Hi Gonzalo,

I had seen this method described but I found that it wasn’t a good way to debug the service start-up in my app for the reasons given in the article. It may work in some other situations though so it may be worth investigating.

Here’s a Code Project article about this technique if anyone is interested: How to debug a windows service and not die in the effort.

By: Gonzalo

Gonzalo — Mon, 29 Oct 2007 22:52:00 +0000

And what about calling debugger methods on “OnStart” ?

Like: System.Diagnostics.Debugger.Launch() or System.Diagnostics.Debugger.Break() …

By: jfrankcarr

jfrankcarr — Fri, 19 Oct 2007 01:01:08 +0000

Thanks for stopping by Michael. I hope you found my article helpful.

By: Michael

Michael — Thu, 18 Oct 2007 21:42:02 +0000

KISS = keep it simple stupid..
that was good advice, I pulled a bunch of start up etc out on OnStart and setup a timer for 30 seconds which then later fires and performs the rest of the initialization including enabling other timers, so now I can set a breakpoint and finally debug the startup /initialization code

thanks