Engineering in the white spaces
____________________________________
A reusable Windows service template - part 3
This is part 3 of a 3-part series that discusses a reusable Windows service template designed to:
- Provide all of the service infrastructure, so that the developer can focus primarily on the real work that the service does.
- Create a service infrastructure that starts/restarts, monitors, and logs the worker thread where the service's work is occurring.
- Isolate the service's work from the controlling infrastructure so that any crash is logged properly and doesn't bring down the service.
- Have relatively simple and small code, so that it's easy to understand, maintain, and debug.
- Enable the developer to test and debug the service within Visual Studio.
- Allow the service to install and uninstall itself from the command-line, without the use of InstallUtil.
- Avoid any cross-thread interactions that involve polling or "busy" loops.
- Reduce application-level cross-thread interactions that involve shared memory.
- Log everything that the service is doing, and especially cross-thread interactions.
11-Oct-2014 17:15
____________________________________
A reusable Windows service template - part 2
This is part 2 of a 3-part series that discusses a reusable Windows service template designed to:
- Provide all of the service infrastructure, so that the developer can focus primarily on the real work that the service does.
- Create a service infrastructure that starts/restarts, monitors, and logs the worker thread where the service's work is occurring.
- Isolate the service's work from the controlling infrastructure so that any crash is logged properly and doesn't bring down the service.
- Have relatively simple and small code, so that it's easy to understand, maintain, and debug.
- Enable the developer to test and debug the service within Visual Studio.
- Allow the service to install and uninstall itself from the command-line, without the use of InstallUtil.
- Avoid any cross-thread interactions that involve polling or "busy" loops.
- Reduce application-level cross-thread interactions that involve shared memory.
- Log everything that the service is doing, and especially cross-thread interactions.
08-Oct-2014 23:50
____________________________________
A reusable Windows service template - part 1
This is part 1 of a 3-part series that discusses a reusable Windows service template designed to:
- Provide all of the service infrastructure, so that the developer can focus primarily on the real work that the service does.
- Create a service infrastructure that starts/restarts, monitors, and logs the worker thread where the service's work is occurring.
- Isolate the service's work from the controlling infrastructure so that any crash is logged properly and doesn't bring down the service.
- Have relatively simple and small code, so that it's easy to understand, maintain, and debug.
- Enable the developer to test and debug the service within Visual Studio.
- Allow the service to install and uninstall itself from the command-line, without the use of InstallUtil.
- Avoid any cross-thread interactions that involve polling or "busy" loops.
- Reduce application-level cross-thread interactions that involve shared memory.
- Log everything that the service is doing, and especially cross-thread interactions.
08-Oct-2014 23:45
