Task Plug-in: A Flexible .NET Plug-in Architecture

• Download demo project - 269.0 KB
• Download source - 512.2 KB

Introduction

I guess I need to start off with the customary, "This is my first CodeProject article, so please be nice." Now that it's been said, let's move on the the meat of this article. The sample project/application was designed to demonstrate the creation of an infrastructure within an application in order to provide some extensibility through plug-ins. This project is hosted on SourceForge. If you wish to contribute to it, provide feedback or alternative approaches, please feel free to contact me. The solution provided, Plug-in, includes five C# projects:

• TaskPluginInterface: The main library.
• TaskPluginTest: An application provided to test the plug-ins.
• FileCopyPlugin: A plug-in created to demonstrate the implementation of ITaskPluginInterface. This plug-in copies one or more files from one directory to another.
• RunCommandPlugin: A plug-in created to demonstrate the implementation of ITaskPluginInterface. This plug-in will run commands using the System.Diagnostics.Process class.
• PluginShellPlugin: This plug-in provides a basic shell for implementing the ITaskPluginInterface.

Technologies used

• Microsoft .NET Framework v2.0, although v1.1 could be used with some modifications.
  • System.configuration
  • System.Reflection
  • System.Collections.Generic
  • System.File.IO
  • System.Diagnostics
  • Delegates, events, and event arguments
  • Log4Net
• Guadagno.Utilties.dll, a series of classes that provides common functionality amongst most of my projects. The key class is ConfigurationBase, which is used for the application configuration.
• SchedulerTime.dll, a class library used for the scheduling. See the reference article below.

Quick and dirty: how-to

Create the plug-in host

Step 1: Include a reference to the TaskPluginInterface.dll in your solution.

Step 2: Get the folder location for the plug-ins. I use \Plugins. Call the Utilities.GetPluginFolder() method.

Step 3: Get a list of plug-ins. Call Utilities.GetPlugins(folderName).

Step 4: Call the plug-ins Execute method.

Create the plug-in

Option 1: code from scratch

Step 1: Include a reference to the TaskPluginInterface.dll in your solution.

Step 2: Create a class that inherits from ITaskPlugin.

public class RunCommand : ITaskPlugin
{
}

Step 3: If you are using Visual Studio 2005, you can use the Intellisense or SmartTag to create the stub implementation of ITaskPlugin.

Step 4: Place your code in the Execute method.

Option 2: use the PluginShellPlugin class

Step 1: Rename the class to what ever name you want.

Step 2: Change the resource file strings to accurately describe your plug-in.

Step 3: Change the code in the DoWork() method.

TaskPluginInterface namespace

ITaskPlugin interface

The ITaskPlugin interface defines the methods, events and properties that the plug-ins must implement.

Methods

Properties

Events

PluginAttribute class

The PluginAttribute class defines the class attributes which can be applied to a class that is implementing the ITaskPlugin interface. This class defines an Attribute, which is PluginType. The PluginType corresponds to the PluginType class. Syntax:

TaskPluginInterface.Plugin(PluginType.Executable)]

public class RunCommand : ITaskPlugin
{

}

Enumerations

ExecuteResult

This enumeration is used as the return value of the Execute method for the ITaskPlugin interface.

PluginType

This enumeration is used to indicate the type of plug-in that is being created. Applying the PluginType attribute to a class does not have an effect the functionality of the class. Its only purpose is to provide a classification of the plug-ins available for list boxes or separate functionality.

PluginEventArgs class

The PluginEventArgs class provides information back to the plug-in host. This information is provided back to the plug-in host via one of the four events. PluginEventArgs properties:

ScheduleConfig class

The ScheduleConfig class provides functions that will load the schedule configuration. Note that this was created for a future version of the application.

Utilities class

The Utilities class provides helper functions to interact with and discover plug-ins. All of the provided methods are static, so there is no need to create an instance of the Utilities class. Utilities class methods:

Included plug-ins

FileCopy

The FileCopy plug-in provides the ability to copy files that fit a mask from one directory to another. This plug-in reads the configuration file, FileCopyPlugin.Settings.xml, for all of the Directory nodes listed in the Directories element. For example:

<Directories>
    <Directory FromDir="C:\Temp\" ToDir="d:\Temp\" FileMask="*.*" />
    <Directory FromDir="C:\Temp\junk" ToDir="d:\Temp\junk" FileMask="*.txt" />
    <Directory FromDir="C:\Temp\junk" ToDir="d:\Temp\junk" FileMask="*.xyz" />
</Directories> 

The following configuration contains three copy commands.

1. Will copy all of the files located in the c:\temp directory to d:\temp
2. Will copy all of the TXT files located in the c:\temp\junk directory to the d:\temp\junk directory
3. Will copy all of the XYZ files located in the c:\temp\junk directory to the d:\temp\junk directory

PluginShell

The PluginShell plug-in provides a class that contains everything needed to implement the ITaskPluginInterface.

RunCommand

The RunCommand plug-in provides the ability to execute processes using the System.Diagnostics.Process namespace. This plug-in reads the configuration file. RunCommandPlugin.Settings.xml, for Command elements listed in the Commands node. Each command element has XmlChildNodes that correspond to parameters of the ProcessStartInfo struct of the Process object.

TaskPluginTest

The TaskPluginTest is a sample application that demonstrates the use of the TaskPluginInterface library. This application utilizes the TaskPluginInterface utilities to load the list of application plug-ins. In addition, this application displays the plug-in metadata, executes the plug-in and handles events from the plug-in.

Future enhancements

• Create NUnit test cases for entire library.
• Create VB.NET sample plug-ins.
• Improve on the Schedule library to allow for the displaying of all future schedules.
• Integrate the ITaskPlugin interface into a Windows Service application to provide a flexible version of the Windows Task Scheduler.

References

• .NET Scheduled Timer by Andy Brummer

History