windows-services

I am currently writing a windows service that runs entirely in the background and does something every day. My idea is that the service should be very stable so if something goes wrong it should not stop but try it next day again and of course log the exception. Can you suggest me any best practice how to make truly stable windows services? I have read the article of Scott Hanselman of exception handling best practice where he writes that there are only few cases when you should swallow an exception. I think somehow that windows service is one of the few cases, but I would be happy to get some

If I rebuild a Windows Service after making changes, can I just copy and replace the old assembly / .exe files to get those changes to run or do I need to re-install the service? Also do I have to first uninstall the service before installing the new version? You don't have to uninstall and reinstall the service since this only adds registry info regarding the executable path and launch options. Just stop the service, copy your assemblies and restart it You do not need to uninstall the service just make changes in your files after stopping the service and then start again it will consider your

I am using Serilog within an TopShelf Service, logging to the console and a rolling file. When running the service in a console my messages are written to the logfile, but when I install the service and run it no logging occurs. Is there anything special I need to configure? The file is written to the binaries folder under ".\logs\log-{date}.txt". Best regards Gope I had a very similar issue. In my case the problem was with relative paths. I just had to specify absolute path. Now it works like a charm. WriteTo.RollingFile(AppDomain.CurrentDomain.BaseDirectory + "\\logs\\log-{Date}.log") Hope

I have this windows service project which's OnStart method looks like this protect void OnStart(string[] args) { IScheduler someScheduler = _schedFactory.GetScheduler(); // _schedFactory is a priva field of the service class IJobDetail someJob = JobBuilder.Create<SomeJob>() .WithIdentity("SomeJob") .Build(); ITrigger someTrigger = TriggerBuilder.Create() .StartAt(new DateTimeOffset(DateTime.UtcNow.AddSeconds(30))) .WithSimpleSchedule(schedule => scheduler.WithIntervalInMinutes(3).RepeatForever()) .Build(); someScheduler.SchedulerJob(someJob, someTrigger); someScheduler.Start(); } I use Visual

I have read in many forums that mapped drives are not accessible from a service as no user is logged on. Question 1) I tried making my service as a log on - as some account and i had my network drive mapped in that very account. The service still cannot access it. Why? Question 2) From the same sevice, i invoke another process. Under what user account will the process run? Thanks 1) Use UNC paths instead, then you do not need access to mapped drive letters. As to why you cannot access them even when running in the same account, it is hard to say for sure without seeing your actual code. 2) it

I've been banging my head against a brick-wall the past 2 days trying to successfully use this example on MSDN: How to: Host WCF in a Windows Service Using TCP If you follow the example through and place the Consumer application within the same solution then it runs successfully - even if the service is turned off ! If the service is switched on and the consumer application is published to say a different network drive then it will not run because the WCF is not listening. The following piece of code in the walk-through is the culprit: protected override void OnStart(string[] args) { if

I am wanting to host my WCF Service Library in a windows service. Although it will be communicating to another wcfservice over a local network. I am having great difficulty in finding recent, up-to-date documentation or help to configure the solution for this purpose. Can anyone advise: a) What the preferred endpoint for this kind of connection? (The other WCF service is hosted using a basicHttpBinding) - this in itself lends itself well to configuring the Castle container through hijacking the global.asax. However, hosting this solution in a windows service means i no longer have access to a