 |
 | I'm still not understanding something...
Ray Mitchell | 13:57 23 Sep '09 |
|
|
I'm afraid I'm too dense for this simple technique. I've seen this solution all over the net but what actually needs to be done still eludes me. Apparently I'm supposed to create an entirely new and unrelated service project and somehow link it to or merge it with the service I actually want to debug. The author mentions reading the entire article, but I couldn't find any more than just the short discussion and examples on the first page.
|
|
|
|
|
| another way to create, debug, instal windows service....
GamePlanner | 15:36 7 Apr '09 |
|
|
|
| Awesome!
Jammer | 5:41 27 Mar '09 |
|
|
|
| time saving and powerful!
thorleifs | 8:56 20 Mar '09 |
|
|
yes! simple things are nice.. time saving and powerful...
thorleifs
|
|
|
|
|
| Extremely helpful .. Caught my admiration
hackrogenius | 11:23 3 Mar '09 |
|
|
yes simpler things are hell nice..time saving and powerful...
i actually loved thread sleeping thing which would catch Timers events ...
Nice example ...
--
ASif Ashraf
MCPD, MCAD.Net
Asif.Log@gmail | hotmail.com
92-306-4526526
Sr. dotNet & Flash Developer
Blu Media Works LHR PK
|
|
|
|
|
| Niceness!
progrez | 23:58 8 Jan '09 |
|
|
OMG! That is soo nice! Saves a bunch of time when debugging services! Thanks man!
|
|
|
|
|
 | Can you use OnStop()???
keith shumway | 9:25 13 Nov '08 |
|
|
Using this Method of debugging a service is there a way from inside the debugger to call the OnStop() Method? I have used your method for debugging a service but am having issues in my Shutdown code and getting the debugger in there to help would be great.
Thanks,
|
|
|
|
|
|
|
It depends on what your bug is.
If it's just a problem within the OnStop then change the call to sleep forever below with a call to your OnStop.
// Put a breakpoint on the following line to always catch
// your service when it has finished its work
System.Threading.Thread.Sleep(System.Threading.Timeout.Infinite);
However if it's the actual calling of OnStop that seems to be the problem, then I'd suggest reading through some of the earlier comments as there are more than a few people who've taken this idea and gone even further with it.
I just love Koalas - they go great with Bacon.
|
|
|
|
|
|
|
My problem is in the code that OnStop() executes (my code to shutdown the service). Since in debug it is not really a service (but an application per this article) I have no way to call OnStop() while in debug. Does that make my question clearer?
|
|
|
|
|
| Excellent Tip..
Member 3978711 | 23:20 16 Oct '08 |
|
|
|
| Nice!
Danie de Kock | 3:12 1 Oct '08 |
|
|
Thanks this  saved me alot of time!
|
|
|
|
|
| Good, but...
Andreas Saurwein Franci Gonçalves | 8:53 30 Sep '08 |
|
|
.. dont ever call SetServiceStatus() or RequestAdditionalTime() if not running under the service process or you earn exceptions.
To avoid them, create new overloads of them in your ServiceBase derived class like:
protected new void RequestAdditionalTime(Int32 nTime)
{
if(!Environment.UserInteractive)
base.RequestAdditionalTime(nTime);
}
Leon[^] - Enterprise Anti-Spam Server
|
|
|
|
|
| Good job
The Ruler | 23:57 18 Jul '08 |
|
|
Very good job Lee. Thanks for an effective solution.
Thanks & Regards,
Viresh Shah
|
|
|
|
|
| ABS love it !!!
izmoto | 2:44 2 Apr '08 |
|
|
Kick ass sample.
love it absolutely. Its really helped me catch some nasty bug. 
void izmoto(char* szKwazi);
|
|
|
|
|
| Another way to do it
Einar Egilsson | 8:14 15 Aug '07 |
|
|
I recently wanted to do something similar. I wanted to be able to run my program as both a windows service and a standalone console application, and be able to debug it without the hassle of installing it as a service. I came up with a way to make it work, that doesn't include special builds, #DEBUG directives, command line parameters or anything like that. I just wrote down my solution at: http://tech.einaregilsson.com/2007/08/15/run-windows-service-as-a-console-program/
Hope it can be useful for someone 
|
|
|
|
|
|
|
A simple approach to debug .NET service!
Thanks
nn coder
|
|
|
|
|
| NICE, EXCELLENT!!!!
Balder1978-2 | 8:54 14 Aug '07 |
|
|
Thank you so much, so easy!
Best regards,
Christian
|
|
|
|
|
| A Cleaner Way?
sstreaker | 3:38 8 Jul '07 |
|
|
I came up with what I think is a cleaner way to do this, perhaps you will agree:
Instead of using the #if compiler conditional to test for debug mode, which is perfect except for (as you mentioned) having to switch between Debug/Release mode all the time, you can use a command-line argument. Set the command line argument to "debugmode" or something simliar on the Debug tab in your project properties, then test for the existence of this argument in Main. Now when you run the project from Visual Studio, the command line arg will be set and you'll always run the non-service code; outside of Visual Studio, your app will run only as a Windows service.
// The main entry point for the process
static void Main(string[] args) {
if(args.Length > 0 && args[0] == "debugmode") {
// Debug code: this allows the process to run as a non-service.
// It will kick off the service start point, but never kill it.
// Shut down the debugger to exit
Service1 service = new Service1();
service.();
// Put a breakpoint on the following line to always catch
// your service when it has finished its work
System.Threading.Thread.Sleep(System.Threading.Timeout.Infinite);
} else {
System.ServiceProcess.ServiceBase[] ServicesToRun;
ServicesToRun = new System.ServiceProcess.ServiceBase[] { new Service1() };
System.ServiceProcess.ServiceBase.Run(ServicesToRun);
}
}
|
|
|
|
|
|
|
Yep that would work - the only issue with it is the extra step to add the commandline argument (trivial) and of course the chance that you may release debug code as a service. With my one it really didn't behave well if you tried to run the debug version as a service - so you knew when you had screwed up and put out a debug build.
|
|
|
|
|
| I dont get it [modified]
TEMoore | 12:57 29 May '07 |
|
|
I cannot get this work at all.
What is Service1 ?
-- modified at 18:04 Tuesday 29th May, 2007
|
|
|
|
|
|
|
If you're simply cutting and pasting from the article - then you won't get anywhere. You need to follow the instructions in the article and create a new C# Windows Service project in Visual Studio, once you've done that you'll be left with a service class called Service1. You would normally change this name to something more suitable and put in your current Service code.
The Service1 code itself would probably look like:
using System;
using System.Collections.Generic;
using System.ComponentModel;
using System.Data;
using System.Diagnostics;
using System.ServiceProcess;
using System.Text;
namespace WindowsService1
{
public partial class Service1 : ServiceBase
{
public Service1()
{
InitializeComponent();
}
protected override void OnStart(string[] args)
{
}
protected override void OnStop()
{
}
}
}
|
|
|
|
|
|
|
Well I have service that is running I am trying make changes to it and need to do debug. The item in the service is OnStart. Which does not work. Error message = No overload for method 'OnStart' takes '0' arguments
|
|
|
|
|
|
|
In which case I'd still recommend building a new service, making the changes I described and then transferring over that 'model' to your existing service. After that read through the comments below which discuss some options related to OnStart.
|
|
|
|
|
| Elegant Solution
John-Howard | 9:16 15 May '07 |
|
|
Nice Work, Thanks!
"Simplicity is the ultimate sophistication" - Leonardo Da Vinci
|
|
|
|
|
| Timer event isn't called
Nicolas Stuardo | 12:13 10 Apr '07 |
|
|
Hello...
I have a Windows Service that in OnStart method set 2 timers that tick when determined time has elapsed.
I can debug OnStart method using your technique, but the timers never get called. Any way to do it?
Thanks
|
|
|
|
|
