I created a 3 service project (below) which uses a project installer for each service. I then added an installer project which installs the services into service manager. Here was my workflow: Create 3 services in a solution in Visual Studio 2008. Naming each service as Service1, Service2 and, Service3. (Being sure to change the … Read more
Here’s the real scoop: A service is a service is a service. That’s my motto. What I mean by that is I don’t care if you are using a C++ EXE, a VB exe, a C# EXE, some thunking host EXE such as SrvAny.exe… they all implement the same API’s to interact with the service … Read more
I agree with Romulo on finishing to start your service as soon as possible. However, if you need the time and you are using .NET Framework 2.0 or later, you might consider ServiceBase.RequestAdditionalTime() method. http://msdn.microsoft.com/en-us/library/system.serviceprocess.servicebase.requestadditionaltime.aspx protected override void OnStart() { this.RequestAdditionalTime(10000); // do your stuff }
You can use the services console, clicking on the left hand side and then selecting the “Connect to another computer” option in the Action menu. If you wish to use the command line only, you can use sc \\machine stop <service>
An MSI is a Windows Installer database. Windows Installer (a service installed with Windows) uses this to install software on your system (i.e. copy files, set registry values, etc…). A setup.exe may either be a bootstrapper or a non-msi installer. A non-msi installer will extract the installation resources from itself and manage their installation directly. … Read more
in C#: var sc = new System.ServiceProcess.ServiceController(“MyService”, “MyRemoteMachine”); sc.Start(); sc.WaitForStatus(System.ServiceProcess.ServiceControllerStatus.Running); sc.Stop(); sc.WaitForStatus(System.ServiceProcess.ServiceControllerStatus.Stopped);
I’ve had problems automating Office from a Windows Service under Windows Server 2008, even though that works fine under Windows Server 2003. The problem also occurs at the Open call, so it may be the same problem. I tried following the advice given by H Ogawa in this MSDN thread, and it seemed to work. … Read more
The following code works for me… no need to prompt for username/password 🙂 <File Id=’JobServiceEXE’ Name=”JobService.exe” DiskId=’1′ Source=”JobService.exe” KeyPath=”yes”/> <ServiceInstall Id=”ServiceInstaller” Type=”ownProcess” Name=”JobService” DisplayName=”123 Co. JobService” Description=”Monitoring and management Jobs” Start=”auto” Account=”[SERVICEACCOUNT]” Password=”[SERVICEPASSWORD]” ErrorControl=”normal” /> <ServiceControl Id=”StartService” Start=”install” Stop=”both” Remove=”uninstall” Name=”JobService” Wait=”yes” /> </Component>
In short, services set to Automatic will start during the boot process, while services set to start as Delayed will start shortly after boot. Starting your service Delayed improves the boot performance of your server and has security benefits which are outlined in the article Adriano linked to in the comments. Update: “shortly after boot” … Read more
Navigate to the installutil.exe in your .net folder (for .net 4 it’s C:\Windows\Microsoft.NET\Framework\v4.0.30319 for example) and use it to install your service, like this: “C:\Windows\Microsoft.NET\Framework\v4.0.30319\installutil.exe” “c:\myservice.exe” Regarding a comment, for 64bit apps, use below: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\installutil.exe