Jay Techy

[ServiceProcessDescriptionAttribute("ServiceControllerDesc")]
public class ServiceController : Component

Remarks

You can use the ServiceController class to connect to and control the behavior of existing services. When you create an instance of the ServiceController class, you set its properties so it interacts with a specific Windows service. You can then use the class to start, stop, and otherwise manipulate the service.

You will most likely use the ServiceController component in an administrative capacity. For example, you could create a Windows or Web application that sends custom commands to a service through the ServiceController instance. This would be useful, because the Service Control Manager (SCM) Microsoft Management Console snap-in does not support custom commands.

After you create an instance of ServiceController, you must set two properties on it to identify the service with which it interacts: the computer name and the name of the service you want to control.

Note
By default, MachineName is set to the local computer, so you do not need to change it unless you want to set the instance to point to another computer.

Generally, the service author writes code that customizes the action associated with a specific command. For example, a service can contain code to respond to an ServiceBase.OnPause command. In that case, the custom processing for the Pause task runs before the system pauses the service.

The set of commands a service can process depends on its properties; for example, you can set the CanStop property for a service to false. This setting renders the Stop command unavailable on that particular service; it prevents you from stopping the service from the SCM by disabling the necessary button. If you try to stop the service from your code, the system raises an error and displays the error message "Failed to stop servicename."

Examples

The following example demonstrates the use of the ServiceController class to control the SimpleService service example. See the ServiceBase class for the example code for the SimpleService service.

using System;
using System.ServiceProcess;
using System.Diagnostics;
using System.Threading;

namespace ServiceControllerSample
{
  class Program
  {
      public enum SimpleServiceCustomCommands
      { StopWorker = 128, RestartWorker, CheckWorker };
      static void Main(string[] args)
      {
          ServiceController[] scServices;
          scServices = ServiceController.GetServices();

          foreach (ServiceController scTemp in scServices)
          {

              if (scTemp.ServiceName == "Simple Service")
              {
                  // Display properties for the Simple Service sample
                  // from the ServiceBase example.
                  ServiceController sc = new ServiceController("Simple Service");
                  Console.WriteLine("Status = " + sc.Status);
                  Console.WriteLine("Can Pause and Continue = " + sc.CanPauseAndContinue);
                  Console.WriteLine("Can ShutDown = " + sc.CanShutdown);
                  Console.WriteLine("Can Stop = " + sc.CanStop);
                  if (sc.Status == ServiceControllerStatus.Stopped)
                  {
                      sc.Start();
                      while (sc.Status == ServiceControllerStatus.Stopped)
                      {
                          Thread.Sleep(1000);
                          sc.Refresh();
                      }
                  }
                  // Issue custom commands to the service
                  // enum SimpleServiceCustomCommands 
                  //    { StopWorker = 128, RestartWorker, CheckWorker };
                  sc.ExecuteCommand((int)SimpleServiceCustomCommands.StopWorker);
                  sc.ExecuteCommand((int)SimpleServiceCustomCommands.RestartWorker);
                  sc.Pause();
                  while (sc.Status != ServiceControllerStatus.Paused)
                  {
                      Thread.Sleep(1000);
                      sc.Refresh();
                  }
                  Console.WriteLine("Status = " + sc.Status);
                  sc.Continue();
                  while (sc.Status == ServiceControllerStatus.Paused)
                  {
                      Thread.Sleep(1000);
                      sc.Refresh();
                  }
                  Console.WriteLine("Status = " + sc.Status);
                  sc.Stop();
                  while (sc.Status != ServiceControllerStatus.Stopped)
                  {
                      Thread.Sleep(1000);
                      sc.Refresh();
                  }
                  Console.WriteLine("Status = " + sc.Status);
                  String[] argArray = new string[] { "ServiceController arg1", "ServiceController arg2" };
                  sc.Start(argArray);
                  while (sc.Status == ServiceControllerStatus.Stopped)
                  {
                      Thread.Sleep(1000);
                      sc.Refresh();
                  }
                  Console.WriteLine("Status = " + sc.Status);
                  // Display the event log entries for the custom commands
                  // and the start arguments.
                  EventLog el = new EventLog("Application");
                  EventLogEntryCollection elec = el.Entries;
                  foreach (EventLogEntry ele in elec)
                  {
                      if (ele.Source.IndexOf("SimpleService.OnCustomCommand") >= 0 |
                          ele.Source.IndexOf("SimpleService.Arguments") >= 0)
                          Console.WriteLine(ele.Message);
                  }
              }
          }


      }
  }
}
// This sample displays the following output if the Simple Service
// sample is running:
//Status = Running
//Can Pause and Continue = True
//Can ShutDown = True
//Can Stop = True
//Status = Paused
//Status = Running
//Status = Stopped
//Status = Running
//4:14:49 PM - Custom command received: 128
//4:14:49 PM - Custom command received: 129
//ServiceController arg1
//ServiceController arg2

CRM work flow set property

1.If you want to send the property values in to custom workflow DLL’s syntax should be like
Field – Entity – Default value : {field (entity); default value}

2. If you just wanted to set the hard coded value
set the Default value {value}

CRM work flow set property

1. If you want to send the property values in to custom workflow DLL’s syntax should be like

Field – Entity – Default value : {field (entity); default value}

2. If you just wanted to set the value

Only you have to set the Default value {value}

Create Simple Windows Service - msdn

Link - http://msdn.microsoft.com/en-us/library/zt39148a.aspx

Walkthrough: Creating a Windows Service Application in the Component Designer

Note
The Windows Service template and associated functionality is not available in the Standard Edition of Visual Studio.

The procedures in this topic demonstrate creating a simple Windows Service application that writes messages to an event log. The basic steps that you perform to create and use your service include the following:

Create a project by using the Windows Service application template. This template creates a class for you that inherits from ServiceBase and writes much of the basic service code, such as the code to start the service.
Write the code for the OnStart and OnStop procedures, and override any other methods that you want to redefine.
Add the necessary installers for your service application. By default, a class that contains two or more installers is added to your application when you click the Add Installer link: one to install the process, and one for each associated service that your project contains.
Build your project.
Create a setup project to install your service, and then install it.
Access the Windows 2000 Services Control Manager and start your service.

To begin, you create the project and set values that are required for the service to function correctly.

Note
Your computer might show different names or locations for some of the Visual Studio user interface elements in the following instructions. The Visual Studio edition that you have and the settings that you use determine these elements. For more information, see Working with Settings.

Creating a Service

To create and configure your service

On the File menu, click New Project.

The New Project dialog box opens.
Select Windows Service in the list of Visual Basic or Visual C# project templates, and name the project MyNewService. Click OK.

Note

The project template automatically adds a component class named Service1 that inherits from System.ServiceProcess.ServiceBase.
Click the designer to select Service1. Then, in the Properties window, set the ServiceName and the (Name) property for Service1 to MyNewService.

Note
The project template automatically adds a component class named Service1 that inherits from System.ServiceProcess.ServiceBase.

Adding Features to the Service

In the next section, you add a custom event log to the Windows service. Event logs are not associated in any way with Windows services. Here the EventLog component is used as an example of the type of component you could add to a Windows service.

To add custom event log functionality to your service

In Solution Explorer, right-click Service1.vb or Service1.cs and select View Designer.
From the Components tab of the Toolbox, drag an EventLog component to the designer.
In Solution Explorer, right-click Service1.vb or Service1.cs and select View Code.

Add or edit the constructor to define a custom event log.

 public MyNewService()
{
InitializeComponent();
if (!System.Diagnostics.EventLog.SourceExists("MySource"))
{    
System.Diagnostics.EventLog.CreateEventSource(
 "MySource","MyNewLog");
}
eventLog1.Source = "MySource";
eventLog1.Log = "MyNewLog";
}

To define what occurs when the service starts

In the Code Editor, locate the OnStart method that was automatically overridden when you created the project, and write code to determine what occurs when the service starts running: