I recommend following pattern for debug: var ServiceToRun = new SomeService(); if (Environment.UserInteractive) { // This used to run the service as a console (development phase only) ServiceToRun.Start(); Console.WriteLine(“Press Enter to terminate …”); Console.ReadLine(); ServiceToRun.DoStop(); } else { ServiceBase.Run(ServiceToRun); } Edit: make sure that your target is Console Application, not Windows Application, otherwise it will … Read more
This is my complete solution, and it works. It is basically the same answer as in this question. using System; using System.Configuration.Install; using System.Reflection; using System.ServiceProcess; using System.IO; namespace ConsoleApplication1 { class Program : ServiceBase { static void Main(string[] args) { AppDomain.CurrentDomain.UnhandledException += CurrentDomainUnhandledException; if (System.Environment.UserInteractive) { string parameter = string.Concat(args); switch (parameter) { case … Read more
A windows service always runs once the computer starts up (as long as it’s so configured). A standard EXE only runs when a user is logged in, and will stop if the user logs out. You would use a windows service for things that always need to run even if nobody is logged in. You … Read more
Add a reference to System.ServiceProcess.dll. Then you can use the ServiceController class. // Check whether the Alerter service is started. ServiceController sc = new ServiceController(); sc.ServiceName = “Alerter”; Console.WriteLine(“The Alerter service status is currently set to {0}”, sc.Status.ToString()); if (sc.Status == ServiceControllerStatus.Stopped) { // Start the service if the current status is stopped. Console.WriteLine(“Starting the … Read more
Before a Windows Service can run, it has to be “installed” first using installutil. EG: C:\installutil -i c:\path\to\project\debug\service.exe Then you can open up the list of Services to start it. EG: Right click ‘My Computer’ Click on ‘Manage’ Open up ‘Services and Applications’ Click on ‘Services’ Find your service in the list and right-click on … Read more
I admit, this problem has been vexing me for some days now. From walking the return values and the contents of GetLastError, I’ve determined that this code should be working correctly according to the system. Because it clearly isn’t (it seems to enter an undefined state that inhibits the service handler from running successfully), I’ve … Read more
Best practice in native code is to call SetServiceStatus with a non-zero exit code to indicate 1) it’s stopped and 2) something went wrong. In managed code, you could achieve the same effect by obtaining the SCM handle through the ServiceBase.ServiceHandle Property and P/Invoke-ing the Win32 API. I don’t see why the SCM would treat … Read more
Yes, you do: .Net framework will read the app.config once, and never touch the app.config again. That is why you have to restart the application to pick up the change. Why does not .Net framework detect that app.config has changed, and refresh all the config data? The reason is simple, this is not possible in … Read more
sc delete “service name” will delete a service. I find that the sc utility is much easier to locate than digging around for installutil. Remember to stop the service if you have not already.
I just had the same problem. It turned out it was because I was running it as a console in debug mode – like the code you have above #if (!DEBUG) #else //debug code #endif And I had compiled it in debug mode and installed the service When I compiled it in release mode it … Read more