Five ways debugging .NET Windows service

re: Three ways debugging .NET Windows service

MichaelGiagnocavo — Wed, 02 May 2007 03:39:10 GMT

What we do is something like #2. You can check Environment.UserInteractive. If it's running as a service, it won't be. We also don't compile as Console. We use Windows Application, but if its UserInteractive, then we call AllocConsole to open up a console window for debugging and other fun.

re: Three ways debugging .NET Windows service

jackbond — Wed, 02 May 2007 09:54:43 GMT

One approach I have found useful was to create an interface that duplicated the standard service events, ie:

interface IServiceProcess

{

Start();

Stop();

Etc();

}

In the actual service implementation, I loaded the classes that implemented IServiceProcess dynamically, and then started them in a loop. This way, I could selectively start and stop various service components either in the service process, or in a test app which could be debugged in Visual Studio. I originally did this for an emulator of a network enabled DVR, which required threads for managing an internal http server and for broadcasting/receiving UPNP messages. Each server process implemented IServiceProcess, and once development was complete on a particular component, I simply added it to the list of modules the service was to run.

re: Five ways debugging .NET Windows service

yaleeyangmsblog — Wed, 02 May 2007 20:26:52 GMT

Thanks for you guys' input. I already added you guys' techniques into the blog.

How To Debug Windows Service OnStart

Notes from the Field — Tue, 22 Jul 2008 05:25:54 GMT

The article, How to: Debug Windows Service Applications details how to attach to a running process to

Debugging Windows Services

dotnet thoughts — Thu, 18 Jun 2009 15:18:24 GMT

In the current project, I have to develop some windows services to sending out notification mails. The