In our current project we have a service that handles messages sent to the application over MSMQ. On startup the service initiates a configurable numbers of listeners that processes messages as they arrive. The main reason this listener initialization is bootstrapped through a Windows Service is because we must be able to “survive” a system shutdown/restart. After a restart the queue listeners must get back to their task of processing and endless stream of messages. I’m not going to go into too much...
Recently I had to initiate some background worker in a Windows Service. Writing a Windows Service with the built in .Net support is a no-brainer. The thing that caught me by surprise was that all the documentation states that I needed to add an installer for the service to run. After a little looking around, it turned out that it is not so difficult to create your own custom installer. I ended up writing a small class that can handle any service and thought I’d share it here. The Windows Service...