Skip to main content

Creating Windows Service using .Net



A service is an application that runs in the background without user interface and start even before user login.

Differences:
                - One can’t simply run with F5. Install service and attach debugger to it.
                - One must create the installer for the service to install and configure.
                - Popup and dialogs are not allowed so log events in Log.
                - Carefully plan about the account and permission for the service.

Creating a Service:
                Create a windows service project.
                Override OnStart, OnStop, and OnPause and other methods.
                Add necessary Installers.
                Build and install.

To Implement the Service:
-              Modify the ServiceBase.ServiceName to unique service name.
-              Add OnStart. Code must return immediately
-              Add code for OnStop
-              Add Code for OnPause, OnContinue, and OnShutDown (All Optionall)

Creating project for service:
A service can’t be directly run. .Net Framework provides ServiceInstaller and ServiceProcessinstaller classes.

ServiceInstaller defines the Name, ServiceName, Description, and Start type.

Use ServiceProcessInstaller to define the service account settings.

1.            R.Click on designer Add Installer
2.            Set the start type Automatic, Manual, Disabled
3.            Set Description and DisplayName
4.            Specify Security Context
a.            Local Service (Limited)
b.            Network Service (Web Server etc.)
c.             Local System (Unlimited)
d.            User (Define login and password or will be prompted on start).
5.            Click Project in Solution Explorer. Select Service Project as Startup Project.
6.            Build then install using MSI package.

To build a setup project:
1.            Add Setup project to current solution
2.            R.Click Setup project in Solution Explorer. Click Add. Click project output.
               Select Service project as primary output
3.            Add Custom Actions to Install Service
a.            R.Clcik Setup project.
b.            View | Custom Actions
c.            In Editor, R.Click Custom Action and Click Add Custom Action.
4.            In Select Item in project Dialog.
a.            Select the application folder
b.            Select the primary output from you service project name
c.            Click OK.
5.            R.Click Setup project and select Build.

Managing Services:

Services can be managed from Computer management.

Service can be also managed from command line.

C:\ Net Start <ServiceName>
C:\ Net Stop <ServiceName>

To Control Services from code use ServiceController class. System.Services.Proecess.ServiceController.

e.g.:
ServiceController sc = new ServiceController (“MyService”);
Sc.Stop();
Sc.Start();
Sc.Pause();
Sc.Continue();

Comments

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...

Using ADO.NET Transaction Object, Saving CLR Objects and SqlNotificationRequest

Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : A transaction can’t span multiple connections.   Local and distributed transaction ares supported in 1.x you have to Enterpeise seveices library to regiser multiple connections and then call EnlistDistributedTransaction. Distributed Transaction Coordinator is required for Distributed transaction that’s available on windows 2000 & +. In 2.X and later use TransactionScope object. Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : Dispoase of the transaction must be called to complete the transaction. Distributed Transaction : ...

Code Access Security in .Net

Namespace: System.Security What is Code Access Security? Code Access Security is a mechanism through which Developers and administrators can restrict code from accessing different resources , without caring about the users’ access level. You can also control resource that can’t be controlled through traditional RBS (Role Based Security), e.g. Web Requests and DNS requests etc. It can be only applied to Managed Applications. These restriction are applied not to the user instead to the Application, thus it does not require username or password. Evidence: It is the information that runtime gather about the assembly to determine which Code Groups the assembly belongs to. The following table shows the common types of evidence that a host can present to the runtime. Evidence Description Application directory The application's installation directory. Hash Cryptographic hash such as SHA1. Publisher Soft...