####Build

####Code quality

####Release

C# Windows Service for scheduling execution of multiple tasks. Allows easy deployment of updates and server management.

• Multiple schedules per task (ex: can run a task more often during certain hours);
• Controlled execution bursts (ex: execute a task up to 10 times per second, until there is no more work available, then wait 10 seconds before next execution)
• Multi-threaded, uses a thread pool, terminates excess threads when idle;
• Plugin architecture, isolates tasks in their own AppDomain and allows updating existing task files without requiring the whole service/other tasks to be shut down (installing new tasks still requires a service restart);
• Monitors filesystem, changes to a file used by a task already loaded (binaries, config file, etc) restarts only that task;
• Provides EventLog (information and errors) and Performance Counter data (number of threads, number of tasks, timeouts/sec, etc);

1. Copy service to a folder and install using ServiceInstall.cmd;

2. Create a new application library project, referencing TaskManager.Common.dll;

3. Create a new class, implement ITaskModule;

4. Create a XML file, using the same name as the library (same file name as the compiled binary, changing the extension from .dll to .xml);

    <?xml version="1.0" encoding="utf-8" ?>
    <tasks>
        <task type="Namespace.ClassName" defaults-go-here>
            <schedules>
                <!-- schedule-specific configuration goes here -->
            </schedules>
            <configuration>
                <!-- task configuration goes here -->
            </configuration>
        </task>
    </tasks>
   

5. Default configuration attributes are specified in the task element (if no schedules are specified in the schedule element, the task will run periodically throughout the whole day using these defaults);

6. Specific schedules are specified inside the schedules element (one schedule element per interval; uses same configuration attributes as the task element, along with a from and to attribute to specify at which time of the day that specific schedule starts and ends);

7. Elements in the configuration element are passed as-is to the Configure method;

8. Build the project and copy the output files to a new folder inside the TaskManager service folder;

9. Start the service; Detected tasks will be recorded in the service Event Log.

You can choose some options to run command-line and Windows services:

• Event log
  • Console: the event messages will be written to console.
  • Windows: the event messages will be written to Windows Event Log system (Event log viewer).
• Statistics
  • Memory: the stats data will be available just in memory. Usefull to debugging purposes or when you do not want any stats overhead.
  • PerformanceCounter: the stats data will be available on .NET performance counters.

####Usage:

• Command-line

TaskManager.exe -e Console -s Memory
TaskManager.exe -e Windows -s PerformanceCounter

• Windows service

You can define parameters on Services Management Console (services.msc), in the properties of your service there is a textbox called "Start parameters":

-e Console -s Memory
-e Windows -s PerformanceCounter

These attributes can be used only inside the task element:

These attributes can be used only inside the schedule element:

These attributes can be used inside both the task and schedule elements:

Providing an App.config file for the library is also supported.

1. What about cron-style schedules?
   • Back in the day, it was requested that the scheduler be configured like that (due to the bursting feature, IIRC). Might add cron-style schedules in the future.

See src/Task.Sample for usage examples.

Licensed under the The MIT License (MIT). In others words, you can use this library for developement any kind of software: open source, commercial, proprietary and alien.